I have just restarted my portal instance and all of sudden the SSO authentication is failing (it had been working perfectly for the past week). When trying to login in to the portal I get an error:
com.sap.mw.jco.JCO$Exception: (103) RFC_ERROR_LOGON_FAILURE: Issuer of SSO ticket is not authorized
I have done a trace in SM50 and get the following error message in the work process developer trace:
N Tue Jul 10 10:59:02 2007
N *** ERROR => ASN.1 blob lengths are not identical. 575 704. [ssoxxkrn.c 1624]
N *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL. [ssoxxkrn.c 847]
N *** ERROR => ASN.1 blob lengths are not identical. 575 704. [ssoxxkrn.c 1624]
N *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL. [ssoxxkrn.c 847]
N *** ERROR => ASN.1 blob lengths are not identical. 575 704. [ssoxxkrn.c 1624]
N *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL. [ssoxxkrn.c 847]
N *** ERROR => ASN.1 blob lengths are not identical. 575 704. [ssoxxkrn.c 1624]
N *** ERROR => Neither was ticket issued by myself nor can I find issuer in TWPSSO2ACL. [ssoxxkrn.c 847]
The problem seems to be caused by the ASN.1 blob length issue - but I can't find any information on this in OSS or on SDN. Anyone have any ideas?
Regards,
Jason
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.