Symptom
- SAML Single Sign On (SSO) does not work and the BI Launchpad login page loads containing an auto populated username different than what is used with the BI Platform: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- Spring SAML logs show the following entry regarding the auto-populated user name:
DEBUG AnonymousAuthenticationFilter:107 - SecurityContextHolder not populated with anonymous token, as it already contained: 'org.springframework.security.providers.ExpiringUsernameAuthenticationToken@46a83297: Principal: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ; Credentials: [PROTECTED]; Authenticated: true; Details: null; Not granted any authorities'
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform (BI) 4.x
- External / Third-party IdentityProvider (IdP)
Product
SAP BusinessObjects Business Intelligence platform 4.2
Keywords
SAML, SSO, Authentication, Windows AD, BI Launchpad,saml2:response , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , 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.
SAP Knowledge Base Article - Preview