Resultado da Busca
28 de jun. de 2022 · The error "Microsoft SQL Server, Error: 18456 <token-identified-principal>" means that the user used to login to SQL Server Management Studio is invalid. It is usually related to an AAD user which is not added on SQL DB that you are trying to connect (User DB or Master DB) or that the AAD user is not the AAD Server Admin.
26 de mai. de 2020 · Even though same name you need to make sure SQL User SID match the AAD Object ID or Application ID (In case of Service Principal or MSI). To fix it you will need to recreate user and grant required permissions
10 de set. de 2022 · Regarding your ask for Error: Login failed for user '<token-identified principal>', it means the user is invalid, usually related to a AAD user that does not have user created on SQL DB that you are trying to connect (User DB or Master DB) or that the user is not the AAD Server Admin.
16 de mar. de 2022 · I receive the "Login failed for user '<token-identified principal>'" error in my Web App logs. If I set the Web App directly as the Azure Active Directory Admin, it can log in successfully. I have installed the MSI Validator through the .scm.
12 de out. de 2022 · I am trying to connect to the Azure sql db using managed identity locally but getting the following error: login failed for user token-identified principal>. I've spent many hours but was unable to find any good solution. Steps I've performed: Set the AD group (which I am part of) as an Admin of the Sql Server.
28 de ago. de 2020 · Found the issue and have resolved it. What happened is the AD group that was assigned as the Active Directory Admin was dropped and created w/ the same name. However, the old group's Object Id wasn't the same as the newly created AD group's Object Id.
18 de mai. de 2023 · I use an App Registration to connect the user via Active Directory, I get the error Login failed for user '<token-identified principal>'. Actually, I get that error regardless, even if I don't log the user in.
