Identityserver4: AllowAnonymous: Bearer was not authenticated. Failure message: No token found.

[Thejacques1]

I have posted this on stack overflow as I thought it might be a question rather than a bug. Can someone please clarify?

So I have a ASP.NET Core 1.1 WebApi secured with IdentityServer4. This works perfectly. However, I am trying to allow certain controllers to be accessed without a bearer token.

In the past I would just add [AllowAnonymous] to the Controller or the end-point, however it seems like IdentityServer's authentication takes precedence.

I keep getting: "IdentityServer4.AccessTokenValidation.Infrastructure.NopAuthenticationMiddleware:Information: Bearer was not authenticated. Failure message: No token found."

I also want to add that the error is received in the API's logging and not in IdentityServer's Logging

Anyone know how I can get around this?

https://stackoverflow.com/questions/45689743/allowanonymous-attribute-overridden-by-identityserver-authentication-net-core

Initially I thought it could relate to this: https://github.com/Microsoft/aspnet-api-versioning/issues/143 . However, even when I downgraded to 1.0.3 of ASP.Net Core it still happens.

[leastprivilege]

It's a logging info message - that's all.

Your authorization rules are not affected by that.

[Thejacques1]

Thanks. The info is misleading. My issue was something else but "Failure message....." gave me the wrong impression. This should be re-worded

[StevenTCramer]

@leastprivilege "It's a logging info message - that's all." Where is it I will do a PR to not show if anonymous. But I can't find the source.

IdentityServer4.AccessTokenValidation.Infrastructure.NopAuthenticationMiddleware I thought that would be the class but I can't find it.

Searching for "was not authenticated" also comes up empty.

[leastprivilege]

Because it is not coming from us - but from the asp.net core authentication system.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.