cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP Status 500 - com.wedgetail.idm.sso.ProtocolException

Former Member
0 Kudos
Hi,

We are In the process of configuring SSO on BO server with the “Windows AD authentication"

 

Manually we are able to login but SSO we are unable to login, window authentication window popup but when i will provide user is and
password manually it will give below mention error:

ERROR

Type Status report

HTTP Status 500- 

message com.wedgetail.idm.sso.ProtocolException:
com.wedgetail.idm.spnego.server.SpnegoException: GSSException: Failure
unspecified at GSS-API level (Mechanism level: com.dstc.security.kerberos.KerberosException:
Successfully matched service principal "sapbotservicesso@ROOT.LOCAL"
but not key type (18) + KVNO (3) in this entry: Principal: [1]
SAPBOTServiceSSO@ROOT.LOCAL TimeStamp: Thu Jan 01 01:00:00 CET 1970 KVNO: -1 EncType:
23 Key: 16 bytes, fingerprint = [af a2 4a 14 6a d7 b8 10 ea 16 ab 1c 48 52 d0
74] )

description The
server encountered an internal error (com.wedgetail.idm.sso.ProtocolException:
com.wedgetail.idm.spnego.server.SpnegoException: GSSException: Failure
unspecified at GSS-API level (Mechanism level:
com.dstc.security.kerberos.KerberosException: Successfully matched service
principal "sapbotservicesso@ROOT.LOCAL" but not key type (18) + KVNO
(3) in this entry: Principal: [1] SAPBOTServiceSSO@ROOT.LOCAL TimeStamp: Thu
Jan 01 01:00:00 CET 1970 KVNO: -1 EncType: 23 Key: 16 bytes, fingerprint = [af
a2 4a 14 6a d7 b8 10 ea 16 ab 1c 48 52 d0 74] )) that prevented it from
fulfilling this

Apache Tomcat 6.0.35

if any one face same problem please share the solution.

Regards

Arpan Saini

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

This error message is normal if you are trying to connect directly on the server where BO is installed.

Try to connect you with an other computer on your network, it will be good.

Regards,

PLM

csk901
Explorer
0 Kudos

Hello PLM,

Could you please explain more on what do you mean by normal. Does it mean due to some configurations like enabling SSO etc? How can we make it work?

Thanks,

CK

Ranganathan
Advisor
Advisor
0 Kudos

Hi,

this will occur if the key tab file is not properly generated.you may need to recreate the keytab file and restart the servers.

thanks

Ranganathan

donka_dimitrova
Contributor
0 Kudos

Hello Arpan Saini,

This forum is for questions and discussions on SAP NetWeaver Single Sign-On product.

The message that you get is not related to SAP NetWeaver Single Sign-On.

You can request support on this problem with creating SAP CSS message or to look for help starting a discussion in the Business Intelligence Solution Architecture forum.

  

Kind regards,

Donka Dimitrova