-
Notifications
You must be signed in to change notification settings - Fork 401
Release Notes 5.0.0
Maria Furman edited this page Apr 19, 2018
·
1 revision
- JsonWebKey: Upgraded to fully support features in http://tools.ietf.org/html/draft-ietf-jose-json-web-key-37
- Logging: Added Event Source based logging in Wilson. IdentityModelEventSource is the exposed event source handle.
- Cryptography: Added support for Elliptical Curve (ECDsa) algorithm.
- Dropped support for WsFederation and Saml.
- SecurityKey is used for token validation instead of SecurityToken.
- CryptoProviderFactory provides all the extensibility to control and customize crypto support.
- Dropped support for reading and writing JWT tokens embedded in XML.
- Removed dependency on System.IdentityModel.dll.
- Replaced JavaScriptSerializer with Json.Net serializer. Deserializing int results in an Int64 object by default instead of Int32.
- Replaced the static ClaimType maps on JwtSecurityTokenHandler with instances.
- Refactoring
- Microsoft.IdentityModel.Protocol.Extensions is refactored into:
- Microsoft.IdentityModel.Protocols: Includes protocol agnostic classes, e.g. ConfigurationManager.
- Microsoft.IdentityModel.Protocols.OpenIdConnect: Includes OpenIdConnect specific support e.g. OpenIdConnectMessage, OpenIdConnectConfiguration, OpenIdConnectProtocolValidator etc.
- System.IdentityModel.Tokens is refactored into:
- Microsoft.IdentityModel.Tokens: Includes support for crypto operations and other classes that are not token format specific e.g. CryptoProviderFactory, TokenValidationParameters etc.
- System.IdentityModel.Tokens.Jwt: Includes classes for handling jwt tokens e.g. JwtSecurityTokenHandler.
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