Replies: 6 comments 5 replies
-
I am also seeing this after migrating Blazor server app fron .net 7 to .net 8. Azure AD B2C give this error: IDX40001: Issuer: 'https://<azure_A2d_name>.b2clogin.com/12345e9a-25bd-4b99-b0cf-4ac6d8b8ac5b/v2.0/', does not match any of the valid issuers provided for this application. It worked previously. Edit: Updated Identity.Web Nuget package today and issue was resolved. |
Beta Was this translation helpful? Give feedback.
-
Did you try 2.15.2 (release yesterday) ? This should solve this issue |
Beta Was this translation helpful? Give feedback.
-
I am experiencing this issue.
I am on |
Beta Was this translation helpful? Give feedback.
-
Same issue with Microsoft.Identity.Web version 2.16.0 |
Beta Was this translation helpful? Give feedback.
-
Has anyone figured out how to solve this? I am having same issue. Using 2.17.0 |
Beta Was this translation helpful? Give feedback.
-
You need to do something extra. See https://github.com/AzureAD/microsoft-identity-web/wiki/Deploying-Web-apps-to-App-services-as-Linux-containers |
Beta Was this translation helpful? Give feedback.
-
I had an ASP.NET Core app hosted in Azure Container Apps that was working with an app registered in an Azure AD B2C instance. When diagnosing a different issue, I had to delete my instance from Azure and redeploy. Now, my app with my exact same configuration, source code, and domains, does not work.
I keep getting the above error after signing in with my sign up and sign in user flow from my application.
In reference to #168, I have tried disabling issuer validation at least temporarily yet to no avail.
Because it was working prior, I can't imagine this is anything but user error, but after poring over the docs, I'm a bit lost on how to next diagnose.
Here is my AzureAD configuration:
dotnet --info
csproj
Beta Was this translation helpful? Give feedback.
All reactions