Skip to Content
0
Former Member
Apr 20, 2007 at 12:04 PM

SSO from EP7 to BSP Application: Pop-Up instead of SSO

53 Views

Dear all,

I'm desperate.

I uploaded the verify.der to my R/3 and added it to the ACL list.

The Portal SID and Client (000) are correct in my R/3

The parameters are set and the machine is restarted with

login/accept_sso2_ticket 1

login/create_sso2_ticket 2

When I connect as a regular user to my BSP application in my portal, the typical pop-up appears that challanges me with my credentials.

SM50 says nothing good:

N Fri Apr 20 13:50:59 2007

N *** ERROR => Verify failed with rc = 5. [ssoxxsgn.c 142]

N uResult=26.

N Certificate not found.

N *** ERROR => MskiDefaultVerify failed with rc = 1703941. [ssoxxsgn.c 216]

N *** ERROR => ValidateTicket returns 1703941. [ssoxxapi.c 220] [ssoxxapi.c 220]

N *** ERROR => Ticket validation failed with rc = 1703941. [ssoxxkrn.c 763]

I don't know WHY?

The /SSOSupport.default Servlet gives me (as the administrator) the following cookie information:

Information of the MYSAPSSO2 Cookie

R/3 User of the MYSAPSSO2 Cookie:

Portal User of the MYSAPSSO2 Cookie: Administrator

System ID of the MYSAPSSO2 Cookie: PP1

System Client of the MYSAPSSO2 Cookie: 000

Timestamp of the MYSAPSSO2 Cookie: 200704201156

Validity of the MYSAPSSO2 Cookie: 8:00

The R/3 User Info is empty! I can't start the servlet as a regular user.

The SSO2 Transaction passes all tests except the ticket throws me a warning:

Something like "The digital signature to this certificate can't be verified".

I reached the end. Do you guys have any helpful hints?

Help is really greatly appreciated and rewarded with points.

Philipp