Dear All,
We are facing some problems with some special SSO requirements. We have a three system landscape (NW 7.4 ABAP only) and in DEV and INT this problem occur: We have a webdynpro ABAP (selfdeveloped) but the problem exists also for all SAP-Webdynpros. If our developers want to test the webdynrpo with SE80 (or also with SICF) SSO is not working, they get the normal login screen in https.They can login and the SSO cookie gets generated but in our PRD System there is no login necessary it they test the same webdynpro in SE80! There is no portal or some other system involved, everything on the same system.
Things we already checked:
- SSO configuration seems to be OK. All necessary Parameters are set:
- login/accept_sso2_ticket = 1
- login/create_sso2_ticket = 2
- icm/host_name_full and SAPLOCALHOSTFULL are set to FQDN
- Test in SE80 (BSP-Application -> SYSTEM_TEST -> test_sso.htm) is OK an MYSAPSSO2 cookie is generated.
- ICM ports (HTTP and HTTPS) are maintained
- Transaction STRUSTSSO2 is maintained and PSE certificate is generated
- Transaction SSO2 is everything green
- Necessary services in SICF are activated
Things we found out:
- If we start transaction SOAMANAGER (which is also a webdynpro) SSO is working fine and the cookie gets generated. If we test the webdynpro by SE80 there is no cookie generated.
- For most webdynpros and also BSPs the browser switches to HTTPS because SSO is not working. If we deactivate HTTPS or change the logon procedure in SICF it is showing the logon page in http instead https but everything else is the same. Also reauthentification is switched of in SICF.
Are there others settings which have to be done that SSO is working in SE80 and SICF?
Thanks a lot!