JwtToken-索赔名称JwtTokenTypes.Subject解析为ClaimTypes.NameIdentifier,这是为什么,如何防止?

Qer*_*rts 2 .net c# jwt

我有这样创建的JwtToken:

        X509Certificate2 cert = certificateStore.Certificate;

        var now = DateTime.UtcNow;
        var tokenHandler = new JwtSecurityTokenHandler();
        var tokenDescriptor = new SecurityTokenDescriptor()
        {
            Subject = new ClaimsIdentity(new[]
            {
                    new Claim(JwtClaimTypes.Subject, upn),
                    new Claim(REQUEST_TYPE_NAME, requestType),
                    new Claim(DOMAIN_NAME, domain),
                }),
            Lifetime = new Lifetime(now, now.AddMinutes(60)),
            SigningCredentials = new X509SigningCredentials(cert),
            TokenIssuerName = ISSUER
        };

        SecurityToken token = tokenHandler.CreateToken(tokenDescriptor);
Run Code Online (Sandbox Code Playgroud)

这是对的。创建令牌,并将其第一个声明命名为“ sub”,它是JwtTokenTypes.Subject的内容。我通过jwt web进行了检查。

问题是,我有这种解决索赔的方法:

        if (string.IsNullOrWhiteSpace(token)) throw new MissingTokenException("Token should not be null.");

        var tokenHandler = new JwtSecurityTokenHandler();
        var securityToken = new X509SecurityToken(new X509Certificate2(new X509RawDataKeyIdentifierClause(certificateStore.Certificate).GetX509RawData()));
        var validationParameters = new TokenValidationParameters()
        {
            IssuerSigningToken = securityToken,
            ValidateAudience = false,
            ValidateActor = false,
            ValidIssuer = ISSUER
        };

        SecurityToken securedToken = new JwtSecurityToken();
        ClaimsPrincipal claimsPrincipal = tokenHandler.ValidateToken(token, validationParameters, out securedToken);

        Claim claim = claimsPrincipal.FindFirst(m => string.Equals(m.Type, REQUEST_TYPE_NAME, StringComparison.OrdinalIgnoreCase));
        if (claim != null && !string.Equals(claim.Value, requestType, StringComparison.OrdinalIgnoreCase))
        {
            throw new MismatchedTokenException("Token is not of the proper type.");
        }

        upn = claimsPrincipal.Claims.FirstOrDefault(m => m.Type.Equals(JwtClaimTypes.Subject) || m.Type.Equals(ClaimTypes.NameIdentifier))?.Value;

        domain = claimsPrincipal.Claims.FirstOrDefault(m => m.Type.Equals(DOMAIN_NAME))?.Value;
Run Code Online (Sandbox Code Playgroud)

在方法的最后,您可以看到我检查了应该为JwtClaimTypes.Subject的声明名称,以及实际上为ClaimTypes.NameIdentifiew的声明名​​称。

您是否知道为什么会发生这种转变或如何防止这种转变?

fbi*_*agi 5

您需要添加以下内容:

JwtSecurityTokenHandler.InboundClaimTypeMap.Clear();
Run Code Online (Sandbox Code Playgroud)

清除了jwt的索赔映射。

完成映射以使jwt声明适应声明的.net类型。如果要避免映射,则要使用身份(IPrincipal.IsInRole或Identity.Name)中的名称和角色,则需要设置声明类型。

您可以在创建ClaimsIdentity时执行以下操作:

    Subject = new ClaimsIdentity(new[]
    {
            new Claim(JwtClaimTypes.Subject, upn),
            new Claim(REQUEST_TYPE_NAME, requestType),
            new Claim(DOMAIN_NAME, domain),
        }, "<auth type>", "name", "role"),
Run Code Online (Sandbox Code Playgroud)

您必须将authType更改为cookie之类的名称,而角色声明名称和名称很可能就是这样。

另一种方法是在令牌验证参数上进行设置:

var validationParameters = new TokenValidationParameters()
    {
        IssuerSigningToken = securityToken,
        ValidateAudience = false,
        ValidateActor = false,
        ValidIssuer = ISSUER,
        NameClaimType = "name",
        RoleClaimType = "role"
    };
Run Code Online (Sandbox Code Playgroud)