SSO failed when you run transaction from SAP GUI which opens a browser session and SSO is expected. The transaction might be NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, etc. You may see the following unexpected page or popup:
- A popup dialog of logon
- A Blank page
- A logon page
In this case, the execution of report SAPHTML_SSO_DEMO will fail also.
Please note there are also some transactions which open browser but are not designed for SSO, such as WEBGUI and newer versions of Solution Manager that use Fiori applications (rather than older versions that used webdynpro applications) for SM_WORKCENTER etc. If the execution of report SAPHTML_SSO_DEMO works well but SSO for one transaction doesn't work in the same ABAP system, it means the transaction is not designed for SSO.
SAP Release Independent
SSO, NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, Logon Ticket, SAPHTML_SSO_DEMO, myssocntl, FQDN, FQHN. , KBA , BC-MID-ICF , Internet Communication Framework , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.