SAP Knowledge Base Article - Preview

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

Symptom

You want to use Single Sign On (SSO) e.g. using X.509 certificate, SAML or SPNego for authentication to Application Server ABAP system, you did the configuration of the SSO, but it doesn't work as expected. Maybe you see:

  • Logon page
  • Logon popup
  • Logon failed page
  • You have to refresh the page to get logon 
  • No redirect to SAML Identity provider 

If you remove all other logon procedure from the logon procedure list in transaction SICF, the SSO is working well.


Read more...

Environment

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

Product

ABAP platform all versions ; SAP NetWeaver all versions ; SAP Web Application Server for SAP S/4HANA all versions

Keywords

ICF service, 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

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.