EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB485225: “KrbException: Cannot locate default realm” error in MicroStrategy Web logs using Kerberos Integrated Authentication and MicroStrategy Web


Pascal Deguine

Principal Product Specialist • Strategy


This article outlines an issue with Kerberos Integrated Authentication error “KrbException: Cannot locate default realm” in MicroStrategy Web.

SYMPTOM


Users attempting to authenticate to Strategy Web using Kerberos Integrated authentication encounter the following error message on the user interface:

ka04W000001IsDYQA0_0EM4W00000399Ub.jpeg

The Strategy Web logs provide additional error context with the message:
<message>Login failure - unable to obtain Kerberos ticket for MSTRSVRSvc/FQDN:34952 - Invalid name provided (Mechanism level: KrbException: Cannot locate default realm)</message>

ACTION


The Kerberos protocol exception “Cannot locate default realm” typically points to a configuration issue related to the krb5.conf file or location. 
The following list shows possible configuration issues that may lead to this issue:
-    Krb5.conf does not contain the realm configuration.
o    Action: Refer to KB33276 and validate krb5.conf content and syntax.
-    krb5.conf file location or permissions not allowing web application to retrieve Kerberos realm information.
o    Action 1: Ensure the correct location to the krb5.conf file is specified in the JVM startup options using the key “-Djava.security.krb5.conf” (refer to KB33276 for additional information)
o    Action 2: Ensure the krb5.conf file permissions are correct for the user running the web application server process.
-    krb5.conf file encoding is not UTF-8.
o    Verify the krb5.conf file encoding to be UTF-8
-    If using Strategy Library on the same web application server, krb5.conf file location may be overwritten by Strategy Library Kerberos configuration
o    Action: Verify Kerberos configuration parameters in the configOverride.properties (<StrategyLibrary>/WEB-INF/classes/config) file of each Strategy Library deployment
 
 


Comment

0 comments

Details

Knowledge Article

Published:

October 14, 2021

Last Updated:

October 14, 2021