Strumpffabrik

Eintrag vom: 09.04.2013.

In this guide we?ll demystify this error by breaking down the most common reasons a "valid" token fails authentication with actionable diagnostics and fixes tailored to ASP.NET Core.

 

With the information provided (unless you?re lucky to have someone that already experienced the same exact error reading this) it?s unlikely for you to receive definitive answer.

 

This error occurs when the API cannot validate the token's signature possibly due to an incorrect algorithm or key. Solution: Check the algorithm used for signing the token in Azure AD and ensure your API is configured to use the same algorithm and keys.

 

In this blog we?ll break down the root causes and provide a step-by-step guide to resolve this issue ensuring seamless authentication between your Angular 7 client and .NET Core 2.2 API. Before diving into fixes let?s demystify the error:

 

This error occurs when the JWT token?s issuer (the party that generated the token) does not match the issuer configured in your .NET Core API. In this blog we?ll break down the root causes of this error walk through step-by-step solutions and ensure you can resolve it quickly during Postman testing.

 

From you query I understand that you are calling custom Web API from Single Page application and getting "invalid token" error while authorizing the Web API. Protected APIs are protected and called by authorized identity only using bearer token which holds the information about authorized identity to validate against protected API.