SAP Knowledge Base Article - Preview

1945794 - How to trace and troubleshoot trusted authentication issues in BI 4.x

Symptom

Trusted authentication requires the following...

  • to be enabled in the global.properties and CMC see KBA 1593628 and KBA 1603002
  • method (query_string, http_header, web_session, remote_user, and user_principal specified in the global.properties)
  • trustedprincipal.conf file with valid shared secret matching the value that was generated in the CMC > authentication > enterprise
  • username (provided depending on the method, the simplest is via URL aka query_string) 

Important to NOTE:  SAP can assist with SAP product issues with trusted authentication such as setting up the enterprise plugin, the trustedprincipal.conf, verifying it works when a username is provided with query_string. However in most cases the username for trusted authentication is provided via 3rd party products and configuration which are outside the scope of SAP support.  Refer to SAP notes 83020 or 1054121 for more information in regards to What is consulting what is support. SAP support can provide "best effort" assistance to help troubleshoot problems with 3rd party products. Issues that are not caused by BI products may not qualify for development support or very high status.


Read more...

Environment

SAP BusinessObjects Business Intelligence Platform 4.x (includes all 4.0, 4.1, future 4.x releases, and patches)

Product

SAP BusinessObjects Business Intelligence platform 4.0 ; SAP BusinessObjects Business Intelligence platform 4.1

Keywords

zie troubleshooting tracing test.jsp logging logs biauth tskba , KBA , tkba , 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 ONE Support launchpad (Login required).

Search for additional results

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