No authenticationScheme was specified and there was no DefaultChallengeScheme found with default authentification and custom authorization

Question

I have a  NET Core 2 0 app and have a problem with authorization  I want to use custom authorization with special requests  Header and standard default authentication  First  I add configuration in Startup cs   public IServiceProvider ConfigureServices IServiceCollection services                   services AddAuthorization options   gt                options AddPolicy DefaultAuthorizedPolicy  policy   gt                        policy Requirements Add new TokenAuthRequirement                             services AddSingleton lt IAuthorizationHandler  AuthTokenPolicy gt                    AuthTokenPolicy cs   public class AuthTokenPolicy   AuthorizationHandler lt TokenAuthRequirement gt           protected override Task HandleRequirementAsync AuthorizationHandlerContext context  TokenAuthRequirement requirement                var filterContext   context Resource as AuthorizationFilterContext          var response   filterContext HttpContext Response          try                          some validation code              var isValidToken   isValidTokenTask Result              if   isValidToken                                response StatusCode   401                  return Task CompletedTask                             response StatusCode   200              context Succeed requirement                     catch  Exception                        return Task CompletedTask                    return Task CompletedTask            and in HomeController cs    Authorize Policy   Startup DefaultAuthorizedPolicy   public async Task lt IActionResult gt  IsVisible     If I use the wrong request header in AuthTokenPolicy I see it  but in the logs I see this error      System InvalidOperationException  No authenticationScheme was specified  and there was no DefaultChallengeScheme found  r n   at Microsoft AspNetCore Authentication AuthenticationService d  11 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Mvc ChallengeResult d  14 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Mvc Internal ResourceInvoker d  19 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Mvc Internal ResourceInvoker d  17 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Mvc Internal ResourceInvoker d  15 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Builder RouterMiddleware d  4 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Diagnostics StatusCodePagesMiddleware d  3 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at React AspNet BabelFileMiddleware d  5 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at Microsoft AspNetCore Authentication AuthenticationMiddleware d  6 MoveNext   r n--- End of stack trace from previous location where exception was thrown --- r n   at System Runtime ExceptionServices ExceptionDispatchInfo Throw   r n   at System Runtime CompilerServices TaskAwaiter HandleNonSuccessAndDebuggerNotification Task task  r n   at core common Middleware LoggingMiddleware d  3 MoveNext   in D  Dev microservicePDP Template core common Middleware LoggingMiddleware cs line 72   After reading Migrating Authentication and Identity to ASP NET Core 2 0 I ve added this code in startup cs  Quotation from the article     services AddAuthentication options   gt         options DefaultScheme   CookieAuthenticationDefaults AuthenticationScheme      options DefaultChallengeScheme   OpenIdConnectDefaults AuthenticationScheme           Define a default scheme in 2 0 if one of the following conditions is true    You want the user to be automatically signed in   You use the  Authorize  attribute or authorization policies without specifying schemes   I added AuthenticationScheme and DefaultChallengeScheme in ConfigureServices    It didn t help  the same error here  I ve tried to use app UseAuthentication    in the Startup Configure   method  with no results   How can I use a custom authorization without authentication

User · Answer

When I used policy before I set the default authentication scheme into it as well. I had modified the DefaultPolicy so it was slightly different. However the same should work for add policy as well.

services.AddAuthorization(options =>
        {
            options.AddPolicy(DefaultAuthorizedPolicy, policy =>
            {
                policy.Requirements.Add(new TokenAuthRequirement());
                policy.AuthenticationSchemes = new List<string>()
                                {
                                    CookieAuthenticationDefaults.AuthenticationScheme
                                }
            });
        });

Do take into consideration that by Default AuthenticationSchemes property uses a read only list. I think it would be better to implement that instead of List as well.

User · Answer

Your initial statement in the marked solution isn t entirely true  While your new solution may accomplish your original goal  it is still possible to circumvent the original error while preserving your AuthorizationHandler logic--provided you have basic authentication scheme handlers in place  even if they are functionally skeletons   Speaking broadly  Authentication Handlers and schemes are meant to establish   validate identity  which makes them required for Authorization Handlers policies to function--as they run on the supposition that an identity has already been established   ASP NET Dev Haok summarizes this best best here   Authentication today isn t aware of authorization at all  it only cares about producing a ClaimsPrincipal per scheme  Authorization has to be aware of authentication somewhat  so AuthenticationSchemes in the policy is a mechanism for you to associate the policy with schemes used to build the effective claims principal for authorization  or it just uses the default httpContext User for the request  which does rely on DefaultAuthenticateScheme    https   github com aspnet Security issues 1469  In my case  the solution I m working on provided its own implicit concept of identity  so we had no need for authentication schemes handlers--just header tokens for authorization  So until our identity concepts changes  our header token authorization handlers that enforce the policies can be tied to 1-to-1 scheme skeletons   Tags on endpoints    Authorize AuthenticationSchemes    AuthenticatedUserSchemeName   Policy    AuthorizedUserPolicyName      Startup cs           services AddAuthentication options   gt                        options DefaultAuthenticateScheme    AuthenticatedUserSchemeName              AddScheme lt ValidTokenAuthenticationSchemeOptions  ValidTokenAuthenticationHandler gt   AuthenticatedUserSchemeName       gt                 services AddAuthorization options   gt                        options AddPolicy  AuthorizedUserPolicyName   policy   gt                                  policy RequireClaim ClaimTypes Sid  authToken                    policy AddAuthenticationSchemes  AuthenticatedUserSchemeName                    policy AddRequirements new ValidTokenAuthorizationRequirement                                 services AddSingleton lt IAuthorizationHandler  ValidTokenAuthorizationHandler gt       Both the empty authentication handler and authorization handler are called  similar in setup to OP s respective posts  but the authorization handler still enforces our authorization policies

User · Answer

Do not use authorization instead of authentication  I should get whole access to service all clients with header  The working code is   public class TokenAuthenticationHandler   AuthenticationHandler lt TokenAuthenticationOptions gt         public IServiceProvider ServiceProvider   get  set         public TokenAuthenticationHandler  IOptionsMonitor lt TokenAuthenticationOptions gt  options  ILoggerFactory logger  UrlEncoder encoder  ISystemClock clock  IServiceProvider serviceProvider             base  options  logger  encoder  clock                 ServiceProvider   serviceProvider             protected override Task lt AuthenticateResult gt  HandleAuthenticateAsync                   var headers   Request Headers          var token    quot X-Auth-Token quot  GetHeaderOrCookieValue  Request            if  string IsNullOrEmpty  token                 return Task FromResult  AuthenticateResult Fail   quot Token is null quot                                   bool isValidToken   false     check token here          if   isValidToken                return Task FromResult  AuthenticateResult Fail    quot Balancer not authorize token   for token  token  quot                        var claims   new      new Claim   quot token quot   token             var identity   new ClaimsIdentity  claims  nameof  TokenAuthenticationHandler            var ticket   new AuthenticationTicket  new ClaimsPrincipal  identity   this Scheme Name           return Task FromResult  AuthenticateResult Success  ticket             Startup cs    region Authentication services AddAuthentication  o   gt        o DefaultScheme   SchemesNamesConst TokenAuthenticationDefaultScheme      AddScheme lt TokenAuthenticationOptions  TokenAuthenticationHandler gt   SchemesNamesConst TokenAuthenticationDefaultScheme  o   gt         endregion  And mycontroller cs  Authorize AuthenticationSchemes   SchemesNamesConst TokenAuthenticationDefaultScheme   public class MainController   BaseController          I can t find TokenAuthenticationOptions now  but it was empty  I found the same class PhoneNumberAuthenticationOptions   public class PhoneNumberAuthenticationOptions   AuthenticationSchemeOptions       public Regex PhoneMask   get  set        new Regex  quot 7  d 10  quot       You should define static class SchemesNamesConst  Something like  public static class SchemesNamesConst       public const string TokenAuthenticationDefaultScheme    quot TokenAuthenticationScheme quot

User · Answer

Many answer above are correct but same time convoluted with other aspects of authN authZ  What actually resolves the exception in question is this line   services AddScheme lt YourAuthenticationOptions  YourAuthenticationHandler gt  YourAuthenticationSchemeName  options   gt                options YourProperty   yourValue

User · Answer

this worked for me      using Microsoft AspNetCore Authentication Cookies     using Microsoft AspNetCore Http   services AddAuthentication CookieAuthenticationDefaults AuthenticationScheme       AddCookie CookieAuthenticationDefaults AuthenticationScheme          options   gt                        options LoginPath   new PathString   auth login                options AccessDeniedPath   new PathString   auth denied

[c#] No authenticationScheme was specified, and there was no DefaultChallengeScheme found with default authentification and custom authorization

Examples related to c#

Examples related to asp.net

Examples related to .net

Examples related to asp.net-core-2.0