Symptom
- Windows AD SSO does not work after configuring as per KBA 2629070 - How to Securely Integrate BI 4.2 or 4.3 with Windows Active Directory and SSO in Distributed Environments - Best Practices
- Following error can be seen in Vintela logs:
- [DEBUG] <TIME STAMP> Start Level Event Dispatcher vintela ([]): Checking service principal: SAP/<SERVICE ACCOUNT> by requesting service ticket for: SAP/<SERVICE ACCOUNT>@<DOMAIN>
- [ERROR] <TIME STAMP> Start Level Event Dispatcher vintela ([]): Successfully got TGT for <SERVICE ACCOUNT>@<REALM> but failed to verify service ticket for SAP/<SERVICE ACCOUNT>
- Exception: com.wedgetail.idm.spnego.server.SpnegoException: GSSException: Failure unspecified at GSS-API level (Mechanism level: com.dstc.security.kerberos.KerberosException: Successfully matched service principal "<SERVICE ACCOUNT>@<REALM>" but not key type (18) + KVNO (2) in this entry:
@
Environment
- SAP BusinessObjects Business Intelligence Platform 4.x
- Microsoft Active Directory 2008 and above
Product
SAP BusinessObjects Business Intelligence platform all versions
Keywords
Vintela, Kerberos, krb, Windows AD, winAd, secWinAD, SSO, single sign on, keytab, authentication, Domain Controler, DC, KDC, realm, Active directory, SPN, AES, kinit, ticket, not key type , 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.