SAP Knowledge Base Article - Preview

2461598 - Logon using SAML fails due to case sensitivity


  • Java system acts as Identity Provider(IdP) and and Ariba Cloud acts as Service Provider(SP).
  • In Ariba system, all user IDs are created in lower case and User IDs in Ariba are case sensitive by design.
  • When a user is authenticated from Portal login page (which is case insensitive for user ID), the Portal (IdP) sends the Login ID in the Name ID parameter of SAML response in mixed case (as it is in the UME) and not in lower case. Since this is sent in mixed case, the Ariba system interprets that this user does not exist and the login fails. 
  • UME used is LDAP.



   SAP Netweaver Java acting as Identity Provider(IDP) and Ariba Cloud as Service Provider(SP).


SAP NetWeaver Application Server for Java all versions


SAML,LDAP,Ariba, SSO, Identity_federation,user_mapping,SAML2.0,SSO_wizard,authentication,UME,active_directory_service,httpwatch, IDP, Identity, Provider, Serivce, token, trace,case_sensitive,upeer_case,lower_case , KBA , BC-JAS-SEC-SML , JAVA SAML 1.1 and 2.0 , BC-JAS-SEC , Security, User Management , Problem

About this page

This 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.