- When setting up Kerberos AD SSO it is suggested to follow KBA 2629070 and previously KBA 1631734 was used
- There are many existing troubleshooting KBA's (explained in detail below) this one focuses on analyzing the web application log for bilaunchpad, opendocument, etc
- If these KBA's prove successful we can add more complicated processes going forward (logging failures, testing more complicated environments, etc)
- The info in these KBA's was searched via free tools textcrawler 3, notepad++ and textpad. There are many tools that can search multiple glf log files including SAP's own Flexilogreader
- To enable web application tracing see KBA 1613472 and not it requires an enterprise logon prior to tracing SSO or other external directories (AD, LDAP, or SAP)
- For AD SSO issues this log is particularly useful when other logs are inconclusive, the stderr.log shows "credentials obtained" and for intermittent issues.
- NEW! to have your web application logs deciphered automatically for you please upload them to the new Support Log Assistant (SLA)
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.”
SAP BusinessObjects Business Intelligence Platform 4.x
zie biauth tskba BOE bobj login authentication groups , KBA , BI-BIP-AUT , Authentication, ActiveDirectory, LDAP, SSO, Vintela , How To
About this pageThis 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.