我对使用新的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
类只接受字符串值?
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);
},
}
}
);
}
答案 0 :(得分:16)
您是否有特定原因要添加新的ClaimsIdentity
?
执行目标的最简单方法是通过ClaimsIdentity
获取通过验证传入令牌生成的ClaimsIdentity claimsId = context.AuthenticationTicket.Identity;
,只需添加声明即可。其余的中间件将负责在会话cookie中将其与其他所有内容串行化,将结果放在当前ClaimsPrincipal
中,以及您尝试手动执行的所有其他操作。
HTH
诉