v2.1.0

• Added new library Sentinel.OAuth.Clients.Mvc5 for easy use with a Sentinel server

v2.0.1

• Fixed bug where scope was ignored when using the authorization code flow

v2.0.0

• Added support for JWT
• Added basic support for OpenID Connect
• Improved hashing algorithms
• Changed datetime handling to use DateTimeOffset to normalize time handling

Breaking changes:

• Added required UserRepository property on SentinelAuthorizationServerOptions. This is used to validate usernames and passwords
• Added required ClientRepository property on SentinelAuthorizationServerOptions. This is used to validate clients
• Added required IssuerUri property on SentinelAuthorizationServerOptions. This should be set to the uri of the site Sentinel is hosted on

v1.5.0

• Improved overall performance (Redis still has some improvements in store)
• Made tests common across all repositories to improve reliability
• Added statistics to track provider performance
• Added repository methods for getting more relevant results when deleting tokens

v1.4.2

• Removed CORS, as Azure API gateways did not play nice when setting CORS in code.
  This means you must take care of making the oauth/token endpoint available from other domains yourself
• Added support for gzip responses when using the Client

1.4.1

• Fixed PrincipalCreated event not being called after authenticating with a refresh token

1.4.0

• Added support for scope parameters. These will be added to the users claims as a urn:oauth:scope claim.
• Added logging to the Redis token manager
• Fixed exception when inserting tokens where RedirectUri was null using the Redis token manager

1.3.1

• Added a new crypto provider using SHA512
• Changed default config to use the new SHA2CryptoProvider for performance reasons

1.3.0

• Previous versions only allowed for a single Authorization Code, Refresh Token and Access Token to exist for a given user and client combination at any given time. This has been rewritten so that the expires_in property can be trusted and your tokens are not suddenly invalidated.
• Rewrote all token managers
• Added new interface ITokenFactory that must be implemented if you want to use custom token classes. See the TokenManagers project for how they are used.

1.2.0

• Rewrote the interfaces to allow for custom token classes
• Added sample tokenmanagers, clientmanagers, usermanagers