diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-06 15:11:09 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-12-06 15:11:09 +0300 |
commit | e9aabbc4b5c80a569ce7e5909bd9d8def11b7a1b (patch) | |
tree | 2bc9ed254deba51c4041c1ee2fb8dcc7bd3dfaad /doc/administration/auth | |
parent | 08608c8e9e9821858dd2f452a3c9ebfb945ab69f (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/auth')
-rw-r--r-- | doc/administration/auth/ldap/ldap-troubleshooting.md | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/administration/auth/ldap/ldap-troubleshooting.md b/doc/administration/auth/ldap/ldap-troubleshooting.md index b4f65699dd0..3f2fe086794 100644 --- a/doc/administration/auth/ldap/ldap-troubleshooting.md +++ b/doc/administration/auth/ldap/ldap-troubleshooting.md @@ -657,6 +657,25 @@ end You can then [run a UserSync](#sync-all-users) **(PREMIUM SELF)** to sync the latest DN for each of these users. +## Could not authenticate from AzureActivedirectoryV2 because "Invalid grant" + +When converting from LDAP to SAML you might get an error in Azure that states the following: + +```plaintext +Authentication failure! invalid_credentials: OAuth2::Error, invalid_grant. +``` + +This issue occurs when both of the following are true: + +- LDAP identities still exist for users after SAML has been configured for those users. +- You disable LDAP for those users. + +You would receive both LDAP and Azure metadata in the logs, which generates the error in Azure. + +The workaround for a single user is to remove the LDAP identity from the user in **Admin > Identities**. + +To remove multiple LDAP identities, use either of the workarounds for the [`Could not authenticate you from Ldapmain because "Unknown provider"` error](#could-not-authenticate-you-from-ldapmain-because-unknown-provider). + ## `Could not authenticate you from Ldapmain because "Unknown provider"` You can receive the following error when authenticating with an LDAP server: |