【问题标题】:Identity Server 4 Cant Validate My Access TokenIdentity Server 4 无法验证我的访问令牌
【发布时间】:2020-12-07 23:44:14
【问题描述】:

我正在使用 Asp.net Core 3.1 Web Api 生成 Api 并使用 Identity Server 4(3.1.2) 和 asp.net identity core 在同一个项目中(都在一个项目中)来验证用户。 Identity Server 4 生成访问令牌,但是当使用 Postman 调用 Api 时,每次都返回 401。 这是我的 Identity Server 4 配置:

 "IdentityServerSetting": {
    "IdentityServerAuthority": "https://localhost:5000",
    "IdentityResources": [
      "openID"
    ],
    "ApiResources": [
      {
        "Name": "MadPay",
        "DisplayName": "MadPay Api",
        "UserClaims": [
          "name",
          "Email"
        ]
      }
    ],
    "Client": [
      {
        "AccessTokenLifeTime": 3600,
        "AllowedGrantTypes": "password",
        "ClientId": "angular",
        "AlwaysIncludeUserClaimsInIdToken": "true",
        "AlwaysSendClientClaims": "true",
        "AllowCorsOrigins": [ "https://localhost:5000" ],
        "RequireClientSecret": "false",
        "AllowedScopes": [ "OpenId", "MadPay" ],
        "AllowOfflineAccess": "true"
      }
    ]
  }

这是我的配置服务

public void ConfigureServices(IServiceCollection services)
        {
            services.Configure<JwtConfig>(_configuration.GetSection(nameof(JwtConfig)));
            services.Configure<IdentityServerSetting>(_configuration.GetSection(nameof(IdentityServerSetting)));

            services.AddScoped<IUnitOfWork, UnitOfWork<ApplicationDBContext>>();

            services.AddMapperConfigurations();
            services.AddServices();

            services.AddDbContext<ApplicationDBContext>(opt =>
            {
                opt.UseSqlServer(_configuration.GetConnectionString("ApplicationConnection"));
            });

            services.AddMvcCore(opt => opt.EnableEndpointRouting = false)
             .SetCompatibilityVersion(CompatibilityVersion.Version_3_0)
             .AddAuthorization()
             .AddNewtonsoftJson(options =>
                    options.SerializerSettings.ReferenceLoopHandling = Newtonsoft.Json.ReferenceLoopHandling.Ignore);

            services.AddResponseCaching();
            services.AddIdentityServerConfig(_identityServerSetting);
            services.AddApiAuthorization();

            services.AddCors();
            services.AddSingleton<IHttpContextAccessor, HttpContextAccessor>();
            services.Configure<ApiBehaviorOptions>(options =>
            {
                options.SuppressModelStateInvalidFilter = true;
            });
        }

这是我的配置

 public void Configure(IApplicationBuilder app, IHostEnvironment env)
        {
            IdentityModelEventSource.ShowPII = true;
            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }
            else
            {
                // The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.
                app.UseHsts();
            }

            //app.UseHsts();

            app.UseCors(i => i.AllowAnyOrigin().AllowAnyMethod().AllowAnyHeader());
            app.AddExceptionHandling();
            app.UseResponseCaching();
            app.UseIdentityServer();
            app.UseHttpContext();
            app.UseHttpsRedirection();
            app.UseStaticFiles();

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "api/{controller}/{action}/{id?}");
            });
        }

AddApiAuthorization 函数

 public static void AddApiAuthorization(this IServiceCollection services)
        {
            services.AddAuthentication(options =>
            {
                options.DefaultScheme = JwtBearerDefaults.AuthenticationScheme;
                options.DefaultChallengeScheme = JwtBearerDefaults.AuthenticationScheme;
            })
                .AddJwtBearer(opt =>
                 {
                     opt.Authority = "https://localhost:5000";
                     opt.RequireHttpsMetadata = false;
                     //opt.Audience = "MadPay";
                     opt.TokenValidationParameters = new TokenValidationParameters
                     {
                         ValidateAudience = false
                     };
                 });

 services.AddScoped<IAuthorizationHandler, PermissionAuthorizationHandler>();

            services.AddAuthorization(option =>
                option.AddPolicy("Permission", builder =>
                    builder.AddRequirements(new PermissionRequirement()).RequireAuthenticatedUser()
                )
            );
}

AddIdentityServerConfig 函数

 public static void AddIdentityServerConfig(this IServiceCollection services, IdentityServerSetting config)
        {
            var finalConfig = MapJsonToConfig(config);

            services.AddIdentity<User, Role>(opt =>
            {
                opt.Password.RequireLowercase = false;
                opt.Password.RequireUppercase = false;
                opt.Password.RequireNonAlphanumeric = false;

                opt.User.RequireUniqueEmail = true;

                opt.SignIn.RequireConfirmedAccount = true;
                opt.SignIn.RequireConfirmedEmail = true;
            })
            .AddEntityFrameworkStores<ApplicationDBContext>()
            .AddUserManager<AppUserManager>()
            //.AddSignInManager<AppSignInManager>()
            .AddErrorDescriber<AppErrorDescriberService>()
            .AddDefaultTokenProviders();

            services.AddIdentityServer(options =>
            {
                options.Events.RaiseErrorEvents = true;
                options.Events.RaiseInformationEvents = true;
                options.Events.RaiseFailureEvents = true;
                options.Events.RaiseSuccessEvents = true;
            })

                    .AddDeveloperSigningCredential()
                    .AddInMemoryIdentityResources(finalConfig.IdentityResources)
                    .AddInMemoryApiResources(finalConfig.Apis)
                    .AddInMemoryClients(finalConfig.Clients)
                    .AddAspNetIdentity<User>()
                    .AddResourceOwnerValidator<AppIdentityPasswordValidator<User>>();
        }

这是来自访问令牌的我的 Paload


{
  "nbf": 1597823415,
  "exp": 1597827015,
  "iss": "https://localhost:5000",
  "aud": "MadPay",
  "client_id": "angular",
  "sub": "1",
  "auth_time": 1597823413,
  "idp": "local",
  "name": "osali",
  "scope": [
    "MadPay",
    "offline_access"
  ],
  "amr": [
    "pwd"
  ]
}

对于调用 Api,请使用此 url:https://localhost:5000/... 并在授权标头中发送令牌:Bearer ....

我认为颁发的访问令牌不是问题。 我花了几天时间,不明白为什么不工作,很困惑出了什么问题!

谢谢你?????????

【问题讨论】:

  • 您可以发布令牌的副本吗?您的邮递员请求是什么样的?您是否在 API 中使用任何授权策略?或者如何保护 API 控制器?
  • 我编辑了我的问题并添加了更多细节。
  • 我在下面更新了我的答案,有帮助吗?

标签: c# asp.net-core asp.net-web-api identityserver4


【解决方案1】:

你可以把所有的token验证参数都设置为false,然后一一启用,看看是什么触发了错误。

            options.TokenValidationParameters.ValidateAudience = false;
            options.TokenValidationParameters.ValidateIssuer = false;
            options.TokenValidationParameters.ValidateIssuerSigningKey = false;
            options.TokenValidationParameters.ValidateLifetime = false;
            options.TokenValidationParameters.ValidateTokenReplay = false;

您也可以尝试启用以下功能并在 postman 或 Fiddler 中检查 API 的响应。

            //True if token validation errors should be returned to the caller.
            options.IncludeErrorDetails = true;

API 控制器如何受到保护?您是否使用任何授权策略?

在您的 API 启动中,您不应使用 IdentityServer,而应使用 AddMyJwtBearer 方法。在您的配置方法中,您应该使用:

        app.UseAuthentication();
        app.UseAuthorization();

这是一个典型 API 的示例 startup.cs 类:

public class Startup
{
    // This method gets called by the runtime. Use this method to add services to the container.
    // For more information on how to configure your application, visit https://go.microsoft.com/fwlink/?LinkID=398940
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddControllersWithViews();

        
        services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
        .AddMyJwtBearer(options =>
        {

            options.Audience = "payment";
            options.Authority = "https://localhost:6001/";

            //True if token validation errors should be returned to the caller.
            options.IncludeErrorDetails = true;

            //If the signing key is not found, do a refresh from the JWKS endpoint
            //This allows for automatic recovery in the event of a  key rollover
            options.RefreshOnIssuerKeyNotFound = true;

            //Gets or sets if HTTPS is required for the metadata address or authority.
            //Should always be true in production!
            options.RequireHttpsMetadata = true;

            //True if the token should be stored in the AuthenticationProperties
            //after a successful authorization.
            options.SaveToken = true;

            //Parameters
            options.TokenValidationParameters.ClockSkew = TimeSpan.FromMinutes(5);
            options.TokenValidationParameters.NameClaimType = "name";
            options.TokenValidationParameters.RoleClaimType = "role";

        });
    }

    // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
    public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
    {
        if (env.IsDevelopment())
        {
            app.UseDeveloperExceptionPage();
        }

        app.UseHttpsRedirection();

        app.UseRouting();

        app.UseAuthentication();
        app.UseAuthorization();


        app.UseEndpoints(endpoints =>
        {
            endpoints.MapControllerRoute(
                name: "default",
                pattern: "{controller=Home}/{action=Index}/{id?}");
        });
    }
}

【讨论】:

  • 这行不通,我将项目添加到 Gitlab,link 以查看所有代码。谢谢
  • 在Api项目中同时使用IdentityServer4和Asp.net Core Identity,如果不使用IdentityServer则localhost:5000/connect/token不能访问也不能生成token
  • this error isnt helfull?trce: IdentityServer4.Hosting.EndpointRouter[0] No endpoint entry found for request path: /api/WeatherForecast
  • 在我的示例中,尝试从 URL 中删除 /api/ 部分。这有帮助吗?或将我的模式更改为模板:“api/{controller}/{action}/{id?}”);我看到您在 GitLab 中的代码使用的是旧的 ASP.NET Core 编码风格。它更现代的使用 app.UseRouting();和 app.UseEndpoints()。
  • 未修复!我的 Api Url 和 Identity Server url 相同:localhost:5000 并且都使用 https,是不是错了??
【解决方案2】:

你在下面缺少:-

app.UseAuthentication();
app.UseAuthorization();

你能在api中的startup.cs配置方法中添加上述方法并尝试一下吗?

【讨论】:

  • @AliBelyani- 你在调用哪个 api 端点?如果它是 weatherForecast 获取端点,您可能需要检查权限属性是否为您提供所需的结果。
猜你喜欢
  • 1970-01-01
  • 1970-01-01
  • 2020-02-06
  • 2018-06-01
  • 2018-09-14
  • 2017-05-14
  • 1970-01-01
  • 2018-07-19
  • 2018-03-08
相关资源
最近更新 更多