Just a quick update about some upcoming changes in IdentityServer3.
The last weeks since the 1.0.0 release in January we did mostly bug fixing, fine tuning and listening to feedback. Inevitably we found things we want to change and improve – and some of them are breaking changes.
Right now we are in the process of compiling these small and big changes to bundle them up in a 2.0.0 release, so hopefully after that we can go back into fine tuning mode without breaking anybody’s code.
Here’s a brief list of things that have/will change in 2.0.0
- Consolidation of some validation infrastructure
- ICustomRequestValidator signature has slightly changed
- Support for X.509 client certificates for client authentication at the token endpoint. This resulted in a number of changes to make client validation more flexible in general
- ClientSecret has been renamed to Secret (we will probably use the concept of secrets in more place than just the client in the future)
- IClientSecretValidator is gone in favour of a more high level IClientValidator
- The event service is now async (we simply missed that in 1.0)
- The CorsPolicy has been replaced by a CORS policy service – along with configurable CORS origins per client
- By default clients have no access to any scopes. You need to configure the allowed scopes (or override by setting the new AllowAccessToAllScopes client flag)
Probable the biggest change is the fact that we renamed the nuget package to simply IdentityServer3. We decided to remove the thinktecture registered trademark from the OSS project altogether (including the namespaces – so that’s another breaking change).
So in the future all you need to do is:
install-package IdentityServer3 (-pre for the time being)
The dev branch on github is now on 2.0.0 and we published a beta package to nuget so you can have a look (in addition to our myget dev feed):
Feedback is welcome!
Pingback: IdentityServer3 2.0.0 released | brockallen