Kerberos Connection Error

[rossw999]

I have a server for which I am having trouble connecting to in DBA Dash.
The error I get is:
Failed to authenticate the user NT Authority\Anonymous Logon in Active Directory (Authentication=ActiveDirectoryIntegrated).

• I can connect successfully in SSMS as myself and also as the service account for DBA Dash
• I can connect successfully in DBA Dash if I use Entra w/ MFA

I can connect to other servers in DBA Dash which have certs and require encrypted connections. This one server is special for some reason. SPNs, and Kerberos bits all seem to check out.

[DavidWiseman]

Do you get the error when adding a source connection in the config tool? If it occurs while using the config tool, it would use the account you are logged in as. Otherwise, it will connect as the service user account. The service user account should be a domain user for Windows authentication to work. Also, the machine running the service should be part of the same domain as the monitored instance (cross domain can work with a trust relationship in place).
Is SSMS running on the same computer as the DBA Dash service account?

[rossw999]

Sorry, yes in config tool.

I have included some screenshots of SSMS and config tool before and after with my user and also the service account. It works in SSMS but not in config.

SSMS is on the same machine as the config tool and is all servers are in the same domain.

[rossw999]

Image #1 - is logged in as my user after I press connect
Image #2 - is logged in as my user before I press connect
Image #3 - is logged in as the service account after I press connect
Image #4 - is logged in as the service account before I press connect

[rossw999]

Thanks for the prompt reply eh!

[DavidWiseman]

I think the DBA Dash connection dialog should have a separate "Microsoft Entra Integrated" option. The "Windows Authentication" option is adding Authentication=ActiveDirectoryIntegrated instead of Integrated Security=True.

I haven't seen Authentication=ActiveDirectoryIntegrated fail in any scenario where Integrated Security=True works. ActiveDirectoryIntegrated is designed to work with Azure AD, but also appears to behave the same as Integrated Security outside of Azure AD. I think we might be seeing a difference here though.

Instead of using the connection dialog, try adding the connection string manually using Integrated Security=True instead of Authentication=ActiveDirectoryIntegrated. e.g.

Data Source=LAB2022;Integrated Security=True;Encrypt=True;Trust Server Certificate=True;Application Name=DBADash

Replace LAB2022 with the name of your SQL instance. Let me know if this works.

[rossw999]

Thank you so much! This server is the only 1 I have had problems with so far, out of 5, and it is the only one which is Azure Connected for Manage Instance Link.

[DavidWiseman]

The connection dialog will be updated in the next version. Windows Authentication will work the same as SSMS and there will be a separate Microsoft Entra Integrated option. I've also added an Advanced option to allow more flexible configuration using a property grid control (Similar to the Advanced option in SSMS)

[DavidWiseman]

The connection dialog is updated in 3.27.3 🚀

[rossw999]

Thanks for all your assistance figuring out the problem and resolving it so quickly.