Cannot Login with Kerberos Principal PLACEHOLDER

After configuring the database for Insights, an error is received when testing the connection from Looker related to a PLACEHOLDER value.

Issue Description

After connecting a database to Looker, a front-end error related to Trouble Loading Data is thrown. Upon further diagnoses, the Looker Connection Test to the DB from the Looker portal fails due to a PLACEHOLDER value, as described below:

Resolution

  1. When using Windows Auth, make sure the SQL server has a SPN entry in AD (as per Insights - SQL Server Configuration documentation).
  2. To verify that the SQL server is using Kerberos authentication, run the following command in SQL:

SELECT auth_scheme FROM sys. dm_exec_connections WHERE session_id = @@SPID

If the above returns 'SQL', use SQL authentication. However, if it returns 'Kerberos', it is known that Windows Authentication is used.

  1. If using Kerberos, ensure that the Kerberos files are located in the Insights folder of the Linux machine.
  2. If the Kerberos files are not there, run the Looker Preinstallation tool and copy the Kerberos files generated after selecting Windows Auth for the DB to the Linux machine.

  1. Unzip the contents of the file into the Insights folder on the Linux machine and run a "docker restart looker-container" command.

If issues are still present, create a UiPath Technical Support ticket and provide updated Looker Logs as well as screenshots of the Insights folder contents on the Linux machine and the Test Connection settings from the Looker Portal.