问题 如何从ASP.Net OpenID连接OWIN组件设置声明?


我对使用新的ASP.Net OpenID Connect框架有疑问,同时在身份验证管道中添加新的声明,如下面的代码所示。我不确定幕后会发生多少'魔术'。我认为我的大部分问题都集中在不了解OWIN认证中间件而不是OpenID Connect上。

Q1。我应该手动设置 HttpContext.Current.User 和 Thread.CurrentPrincipal 从 OwinContext.Authentication.User

Q2。我希望能够像以前一样将对象类型添加到声明中 System.IdentityModel.Claims.Claim。新的 System.Security.Claims.Claim class只接受字符串值?

Q3。我需要使用新的 SessionSecurityToken 我的包装纸 ClaimsPrincipal 在 System.Security.Claims.CurrentPrincipal 序列化为cookie - 我正在使用 app.UseCookieAuthentication(new CookieAuthenticationOptions()); 但现在确定在维持我在此期间添加的任何其他声明方面的确切做法 SecurityTokenValidated 事件?

    public void ConfigureAuth(IAppBuilder app)
    {
        app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);
        app.UseCookieAuthentication(new CookieAuthenticationOptions());
        app.UseOpenIdConnectAuthentication(
            new OpenIdConnectAuthenticationOptions
            {
                ClientId = clientId,
                Authority = authority,
                PostLogoutRedirectUri = postLogoutRedirectUri,

                Notifications = new OpenIdConnectAuthenticationNotifications()
                {
                    SecurityTokenValidated = (context) =>
                    {
                        // retriever caller data from the incoming principal
                        var UPN = context.AuthenticationTicket.Identity.FindFirst(ClaimTypes.Name).Value;
                        var db = new SOSBIADPEntities();

                        var user = db.DomainUser.FirstOrDefault(b => (b.EntityName == UPN));

                        if (user == null)
                        {
                            // the caller was not a registered user - throw to block the authentication flow
                            throw new SecurityTokenValidationException();
                        }

                        var applicationUserIdentity = new ClaimsIdentity();
                        applicationUserIdentity.AddClaim(new Claim(ClaimTypes.Name, UPN, ""));
                        applicationUserIdentity.AddClaim(new Claim(ClaimTypes.Sid, user.ID.ToString(CultureInfo.InvariantCulture)));


                        var applications =
                            db.ApplicationUser
                            .Where(x => x.ApplicationChild != null && x.DomainUser.ID == user.ID)
                            .Select(x => x.ApplicationChild).OrderBy(x => x.SortOrder);

                        applications.ForEach(x =>
                            applicationUserIdentity.AddClaim(new Claim(ClaimTypes.System, x.ID.ToString(CultureInfo.InvariantCulture))));

                        context.OwinContext.Authentication.User.AddIdentity(applicationUserIdentity);

                        var hasOutlook = context.OwinContext.Authentication.User.HasClaim(ClaimTypes.System, "1");

                        hasOutlook = hasOutlook;

                        HttpContext.Current.User = context.OwinContext.Authentication.User;
                        Thread.CurrentPrincipal = context.OwinContext.Authentication.User;

                        var usr = HttpContext.Current.User;

                        var c =  System.Security.Claims.ClaimsPrincipal.Current.Claims.Count();


                        return Task.FromResult(0);
                    },
                }
            }
        );
    }

3609
2017-11-28 22:59


起源



答案:


是否有特定原因要添加新的 ClaimsIdentity

做你目标的最简单方法是检索 ClaimsIdentity 通过验证传入令牌生成的 ClaimsIdentity claimsId = context.AuthenticationTicket.Identity; 一旦你拥有它,只需添加声明。其余的中间件将负责在会话cookie中将其与其他所有内容一起序列化,将结果放在当前 ClaimsPrincipal,以及你似乎试图手动完成的所有其他事情。
HTH
V.


14
2017-11-29 04:39