You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using Microsoft Entra ID (AzureAD) authentication with multi-tenancy (i.e. no tenant ID is specified, "common" or "organizations" is used instead), token validation fails during login:
IDX10205: Issuer validation failed because the actual issuer didn't match the valid issuer(s). Issuer: 'System.String (value removed)'. Did not match: validationParameters.ValidIssuer: 'System.String (value removed)' or validationParameters.ValidIssuers: 'System.String (value removed)'
The Orchard documentation explicitly states multi-tenant accounts as supported.
To Reproduce
Steps to reproduce the behavior:
Create an Azure App registration with Supported account types set to Accounts in any organizational directory.
Configure Microsoft Entra ID authentication in Orchard with the application ID only. Set the tenant ID to common instead of the actual tenant.
gvkries
changed the title
Multi-tenant Microsoft Entry ID authentication not working
Multi-tenant Microsoft Entra ID authentication not working
Dec 1, 2023
gvkries
added a commit
to gvkries/OrchardCore
that referenced
this issue
Dec 1, 2023
Describe the bug
When using Microsoft Entra ID (AzureAD) authentication with multi-tenancy (i.e. no tenant ID is specified, "common" or "organizations" is used instead), token validation fails during login:
The Orchard documentation explicitly states multi-tenant accounts as supported.
To Reproduce
Steps to reproduce the behavior:
common
instead of the actual tenant.Expected behavior
Login should work out of the box.
This can easily be fixed by using the
AadIssuerValidator
that comes withMicrosoft.Identity
(see https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki/ValidatingTokens#dx10205-issuer-validation-failed).Additionally, this would allow to use any other Microsoft accounts (e.g. personal Microsoft accounts, Skype, XBox).
The text was updated successfully, but these errors were encountered: