Spotfire server fails to start with "Failure acquiring a Kerberos TGT for the service principal" error after the upgrade

Spotfire server fails to start with "Failure acquiring a Kerberos TGT for the service principal" error after the upgrade

book

Article ID: KB0078020

calendar_today

Updated On:

Products Versions
Spotfire Server All Supported Versions

Description

Upgrading Spotfire Server that is configure with Kerberos authentication to another version, the server may fail to start with the following error message in server.log
-----------------------------------------

ERROR 2019-02-15T10:07:04,007-0700 [*Initialization*] web.context.ContextLoader: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kerberosCredentialsManager' defined in class path resource [applicationContext.xml]: Bean instantiation via constructor failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.server.security.KerberosCredentialsManager]: Constructor threw exception; nested exception is com.spotfire.server.ServerInitializationException: Failure acquiring a Kerberos TGT for the service principal

Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.spotfire.server.security.KerberosCredentialsManager]: Constructor threw exception; nested exception is com.spotfire.server.ServerInitializationException: Failure acquiring a Kerberos TGT for the service principal

Caused by: com.spotfire.server.ServerInitializationException: Failure acquiring a Kerberos TGT for the service principal

Caused by: javax.security.auth.login.LoginException: No CallbackHandler available to garner authentication information from the user


----------------------------------------

Issue/Introduction

Spotfire server fails to start with "Failure acquiring a Kerberos TGT for the service principal" error after the upgrade

Environment

All Supported Environments

Resolution

One of the reasons for this issue is due to unconfigured krb5.conf file and missing keytab file in the upgraded Spotfire Server location. Make sure to copy the krb5.conf and keytab files from the existing "[Spotfire Server installation folder\jdk\jre\lib\security" folder to the "\jdk\jre\lib\security" folder location of the upgraded Spotfire server folders.

Note: This is based on the assumption that the new version of the Spotfire Server is installed on the same machine as the old one.
Note: If this doesn't resolve the issue, enable debug logging on the Spotfire Server and check the server logs for additional clues. Review the Spotfire Server Installation and Configuration manual for additional information on logging and monitoring.