-
Notifications
You must be signed in to change notification settings - Fork 401
SecurityTokenInvalidSignatureException: IDX10511
BrentSchmaltz edited this page Oct 18, 2018
·
2 revisions
This exception message can be generated when a 'JsonWebKey' has a modulus of size 257 bytes and the first byte is a '0' (ZERO).
For example:
var jsonWebKey = new JsonWebKey
{
KeyId = "xneUh4tPkUPsVH/okK+VMrXirVA=",
Kid = "xneUh4tPkUPsVH/okK+VMrXirVA=",
N = "ALq7LDOgZRirsfc308DI_hSwSRZsYpPhiD69WyA65s-wRpG276x5SoWeyMOZJMi4qz2CG6K51_mHov0ZFmdN3sXARQPOgvepwQ1hY2OPRVmWzitdAP3b_UDuJR_rBIsSXVjnaDOdF_y9vefmVWanDh3Aef5Dk_0TzPexMod_WbEgcnibIgg4aZMSUeFsAViYkYSfgXrF16nZm2A3QJTbSuFTGpr9VPVLdD7mRvBgNXhm117OTg5OIBzRUnLrKlcqIg41uPdFHxNCJI3ukfyw9hvoHb1qCdAO3I9L66ZXdXTjY6uhoqgP_OGo6ze3BpQtIcECInNU7qkNd8CJ_MMRqgE",
Alg = "RS256",
E = "AQAB",
Kty = "RSA",
Use = "sig"
};
Conceptual Documentation
- Using TokenValidationParameters.ValidateIssuerSigningKey
- Scenarios
- Validating tokens
- Outbound policy claim type mapping
- How ASP.NET Core uses Microsoft.IdentityModel extensions for .NET
- Using a custom CryptoProvider
- SignedHttpRequest aka PoP (Proof-of-Possession)
- Creating and Validating JWEs (Json Web Encryptions)
- Caching in Microsoft.IdentityModel
- Resiliency on metadata refresh
- Use KeyVault extensions
- Signing key roll over