cancel
Showing results for 
Search instead for 
Did you mean: 

MYSAPSSO2 Not available when called from Portal

Former Member
0 Kudos

Hello,

I'm not getting MYSAPSSO2 cookie when my R3 BSP is called from Portal using BSP iView.

Initial login in portal is validated against CRM (user id and password exists in CRM). Portal login user exists in R3 but password is disabled in R3. In RZ10 parameters login/accept_sso2_ticket is set 1 and login/create_sso2_ticket is set to 0 (The idea here is R3 will not create ticket but only accept ticket)

In HTML trace, I can see MYSAPSSO2. When testing using SYSTEM_TEST, popup comes up prompting for user id and password.

What could be the issue here? Can R3 accept and pass on logon ticket created by CRM as currently configured in our system? How to make sure the user is set up correctly for single sign on (in Portal-CRM-R3 environment) and how to make sure iView and R3 is configured correctly.

Any help will be greatly appreciated.

Regards

Ramesh

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Closing the thread

Former Member
0 Kudos

SAP has confirmed cookie will not be sent in such scenarios. Closing the thread.

Ramesh

athavanraja
Active Contributor
0 Kudos

you need to set login/create_sso2_ticket also to 1. this is required for SSO to work.

only if this parameter is set , the system will create mysapsso2 cookie

Former Member
0 Kudos

Hello,

We set that flag. Still no use. I tested SYSTEM_TEST. When I call test_sso2.htm by typing the URL in the browser, it says logon ticket found and displays MYSAPSSO2. Then I created an iView in the portal and configured it to call SYSTEM_TEST and page test_sso2.htm. Now no ticket found.

Logon ticket is not working when the BSP is called from Portal. In the trace we call see MYSAPSSO2 but it is not available. What we should do to get MYSAPSSO2 when called form Portal?

Thanks