.NET Core OpenId Connect Server:跨多个应用程序共享相同的令牌

时间:2017-07-11 11:24:15

标签: oauth asp.net-core openid-connect aspnet-contrib

我有两个用.NET Core编写的api,目标是4.6.1:

  1. myAuthApi(http://localhost:8496):用于验证凭据并向客户发放令牌。它还有一个端点/ api / values / 1(此操作的Authorize属性,用于验证令牌)
  2. myPublicApi(http://localhost:8497):在/ api / values / 1上接收来自客户端的令牌(此操作的Authorize属性,也用于验证令牌)。 myPublicApi没有任何令牌端点,并且是资源服务器。
  3. 我使用的是AspNet.Security.OpenIdConnect.Server 1.0.0。 这两个API都是Service.Fabric无状态服务

    我可以使用以下请求格式成功获取令牌http://localhost:8496/connect/token

    client_id=XX&client_secret=XXX&grant_type=password&username=XXX&password=XXX
    

    在针对myAuthApi(http://localhost:8496/api/values/1)验证令牌时,它可以正常工作。但是,当对myPublicApi(http://localhost:8497/api/values/1)使用相同的令牌时,它不会。

    在两个API中,在Startup.cs中,我有

        // This method gets called by the runtime. Use this method to add services to the container.
        public void ConfigureServices(IServiceCollection services)
        {
            // Connect to Redis database.
            var redis = ConnectionMultiplexer.Connect(ConnectionHelper.GetRedisConnectionString(Configuration));
            services.AddDataProtection()
                .PersistKeysToRedis(redis, "DataProtection-Keys")
                .ProtectKeysWithCertificate(CertificateHandler.GetX509Certificate2(Configuration));
    
            // Add framework services.
            services.AddMvc().AddJsonOptions(opts =>
            {
                // we set the json serializer to follow camelCaseConventions when 
                // receiving /replying to JSON requests
                opts.SerializerSettings.ContractResolver = new CamelCasePropertyNamesContractResolver();
            });
            // we add authentication for the oAuth middleware to be registered in the DI container
            services.AddAuthentication();
        }
    

    在myPublicApi中,我有:

        // This method gets called by the runtime. Use this method to configure the HTTP request pipeline.
        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
    
            // Add a new middleware validating access tokens.
            app.UseOAuthValidation(options =>
            {
                // Automatic authentication must be enabled
                // for SignalR to receive the access token.
                options.AutomaticAuthenticate = true;
                options.Events = new OAuthValidationEvents
                {
                    // Note: for SignalR connections, the default Authorization header does not work,
                    // because the WebSockets JS API doesn't allow setting custom parameters.
                    // To work around this limitation, the access token is retrieved from the query string.
                    OnRetrieveToken = context =>
                    {
                        // Note: when the token is missing from the query string,
                        // context.Token is null and the JWT bearer middleware will
                        // automatically try to retrieve it from the Authorization header.
                        context.Token = context.Request.Query["access_token"];
    
                        return Task.FromResult(0);
                    }
                };
            });
    
            app.UseMvc();
        }
    

    在myAuthApi中我有:

        public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
            // Add a new middleware validating access tokens.
            app.UseOAuthValidation(options =>
            {
                // Automatic authentication must be enabled
                // for SignalR to receive the access token.
                options.AutomaticAuthenticate = true;
                options.Events = new OAuthValidationEvents
                {
                    // Note: for SignalR connections, the default Authorization header does not work,
                    // because the WebSockets JS API doesn't allow setting custom parameters.
                    // To work around this limitation, the access token is retrieved from the query string.
                    OnRetrieveToken = context =>
                    {
                        // Note: when the token is missing from the query string,
                        // context.Token is null and the JWT bearer middleware will
                        // automatically try to retrieve it from the Authorization header.
                        context.Token = context.Request.Query["access_token"];
    
                        return Task.FromResult(0);
                    }
                };
            });
    
            // Add a new middleware issuing access tokens.
            app.UseOpenIdConnectServer(options =>
            {
                options.Provider = new AuthenticationProvider();
                // Enable the logout, token and userinfo endpoints.
                options.LogoutEndpointPath = "/connect/logout";
                options.TokenEndpointPath = "/connect/token";
                options.UserinfoEndpointPath = "/connect/userinfo";
                CertificateHandler.SetupCommonAuthServerOptions(options, Configuration);
            });
    
            app.UseMvc();
        }
    

    正如您所看到的,我的数据保护提供程序正在将密钥存储在Redis中,而我正在使用我在2个应用程序中共享的证书来保护密钥。 资源服务器未配置任何身份验证提供程序,并且在启动时没有UseOpenIdConnectServer。在asp.net Web API 2中,令牌解密过去是使用共享机器密钥在应用程序之间进行管理的。

    如何使用oAuthValidation在所有其他应用中成功验证myAuthApi发出的令牌?

    编辑,这里可以看到一些日志: https://pastebin.com/ACDz1fam

    EDIT2: 在彻底阅读了日志之后,我发现令牌的不受保护是使用相同的数据保护提供程序,但用途不同:

    "Performing unprotect operation to key {4406cfa7-a588-44ba-b73a-e25817d982d9} with purposes ('C:\SfDevCluster\Data\_App\_Node_4\TestMicroServicesType_App22\PublicApiPkg.Code.1.0.1', 'OpenIdConnectServerHandler', 'AccessTokenFormat', 'ASOS')."
    "Performing unprotect operation to key {4406cfa7-a588-44ba-b73a-e25817d982d9} with purposes ('C:\SfDevCluster\Data\_App\_Node_3\TestMicroServicesType_App22\AuthApiPkg.Code.1.0.1', 'OpenIdConnectServerHandler', 'AccessTokenFormat', 'ASOS')."
    

    要解决此问题,@ PinpointTownes建议设置数据保护提供程序,如下所示:

        var redis = ConnectionMultiplexer.Connect(ConnectionHelper.GetRedisConnectionString(Configuration));
        services.AddDataProtection()
                 // set the application name to a common value in all apps 
                 // to have the same purpose and share the token across apps
                .SetApplicationName("MyTestMicroServices")
                .PersistKeysToRedis(redis, "DataProtection-Keys")
                .ProtectKeysWithCertificate(CertificateHandler.GetX509Certificate2(Configuration)); 
    

1 个答案:

答案 0 :(得分:1)

调用services.AddDataProtection().SetApplicationName("[your application name]")以确保您的两个API使用相同的鉴别器(用于派生加密密钥),它应该可以工作。