2544749 - Single Sign On authentication doesn't work as expected for Browser access to Application Server ABAP

It is recommended to utilize Single Sign On (SSO) methods such as X.509 certificate, SAML, or SPNego for authentication to the Application Server ABAP system. After configuring the SSO, it may not function as anticipated. Possible issues that may arise include encountering a logon page, logon popup, logon failed page, the need to refresh the page for logon, or the absence of redirection to the SAML Identity provider. To resolve this, removing all other logon procedures from the logon procedure list in transaction SICF will ensure the SSO operates smoothly.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

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

ICF, Internet Communication Framework, Service, Services, ICF service, ICF_GDPR, ICF_STD, Logon Procedure, SICF, Client Certificate, Basic Authentication, Fiori, App, ui2, ui5, prompt for x509 certificates, windows, kerberos, nwbc, webgui, ushell, saml, spnego, azure, AD, fails, redirect, identity provider, idp, sap-ssolist=XXX, Your browser is not configured for using SPNego</H1>Press F5 (Page Refresh) to continue. GetServerInfo   , KBA , BC-MID-ICF , Internet Communication Framework , BC-SEC-LGN , Authentication , Problem