Symptom
- Windows Active Directory (AD) single sign-on not working
- Following snippet can be seen in Tomcat Stderr logs:
- [DEBUG] jcsi.kerberos: Found name servers using JNDI
[DEBUG] jcsi.kerberos: KDC1_HOSTNAME (KDC1_IP)
[DEBUG] jcsi.kerberos: ** requesting initial ticket .. **
[DEBUG] jcsi.kerberos: ** creating AS request .. **
for client: YOUR_PRINCIPAL
at realm: YOUR_REALM
[DEBUG] ** Sending request to KDC .. **
[DEBUG] Resolving KDC for realm: YOUR_REALM
- [DEBUG] jcsi.kerberos: Found name servers using JNDI
- Windows AD manual login works
Read more...
Environment
- SAP BusinessObjects Business Intelligence Platform 4.x
- SAP BusinessObjects Business Intelligence Platform 2025
Product
SAP BusinessObjects Business Intelligence platform 4.2 ; SAP BusinessObjects Business Intelligence platform 4.3
Keywords
BI launchpad, Launch pad, BILP, WinAD, secWinAD, KDC, Domain Controller, Active Directory, CMC, Open Document, BILaunch pad, Realm, KRB5.ini, _ldap._tcp.YOUR_REALM, _kerberos._tcp.YOUR_REALM, _kerberos._udp.YOUR_REALM , 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