[Muhammad Maaz (top answer)] I was facing the same issue. i was missing the authority..make sure authority and api name is correct now this code in configure services in startup file works for me: ``` services.AddAuthentication(IdentityServerAuthenticationDefaults.AuthenticationScheme) .AddIdentityServerAuthentication( x => { x.Authority = "YOUR_HOST (port 5000)"; //idp address x.RequireHttpsMetadata = false; x.ApiName = "api2"; //api name }); ```

Context: Stack Overflow #58563661 (top answer, 22 votes, 13 answers): I have an Angular 7 application interfacing with a .Net Core 2.2 API back-end. This is interfacing with Azure Active Directory. On the Angular 7 side, it is authenticating properly with AAD and I am getting a valid JWT back as verified on jwt.io. On the .Net Core API side I created a simple test API that has [Authorize] on it. When I call this method from Angular, after adding the Bearer token, I am getting (as seen in Chrome Debug Tools, Network tab, "Headers"): WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found" With a HTTP/1.1 401 Un