2460180 - SSO failed in transaction NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, ILM_SB etc.

SSO failed when running transactions from SAP GUI which opens a browser session and SSO is expected.
The transaction might be NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, ILM_SB etc. 
The following unexpected page or popup is shown:

• A popup dialog of logon
• A Blank page
• A logon page
• Can’t connect securely to this page. This might be because the site uses outdated or unsafe TLS security settings.

In this case, the execution of report SAPHTML_SSO_DEMO will fail also.

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 Web Dynpro 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 that the transaction is not designed for SSO.

• SAP NetWeaver
• SAP NetWeaver Application Server for SAP S/4HANA
• ABAP PLATFORM - Application Server ABAP

ICF, Internet Communication Framework, SICF, Service, Services, ICF service, ICF_GDPR, SSO, NWBC, SOAMANAGER, SOLMAN_SETUP, SM_WORKCENTER, DBACockpit, Logon Ticket, SAPHTML_SSO_DEMO, myssocntl, FQDN, FQHN, SOLMAN_WORKCENTER, rz10, rz11, login/create_sso2_ticket, /sap/public/myssocntl, icm/host_name_full, SAPLOCALHOSTFULL , KBA , mysapsso2 , BC-MID-ICF , Internet Communication Framework , Problem