It’s busy times right now but we are still on track with our release plans for IdentityServer (and IdentityManager, which will get more love once IdentityServer is done). In fact we just pushed beta 3-4 to github and nuget, which mostly contains bug fixes and merged pull requests.
The other big news is that both projects joined the .NET Foundation as part of the announcements around open sourcing .NET. Joining the Foundation provides us with a strong organizational backbone to increase the visibility and attractiveness of IdentityServer and IdentityManager to both, new users and new committers. As a current user of one of these projects, this will provide even stronger long-term safety of your investments in the use of these frameworks.
If you want to contribute to any of the projects – you are more than welcome! Please have a look at our contribution guidelines and don’t hesitate to get in touch with us!
Also big thanks to our contributors – and especially Damian Hickey and Hadi Hariri who proved this week that this whole community thing is actually working!
Today we had a chance to sit together with the ASP.NET team and try moving IdentityServer to vNext.
There are two fundamental approaches for doing that – migrate the code and middleware to the new APIs or host IdentityServer as-is as an OWIN component.
We went for the latter – and lo and behold – after two hours we got everything up and running. Big thanks to Chris, Lou and Dan from the ASP.NET team!
This allows us (at least for the time being) to run IdentityServer on both ASP.NET vCurrent as well as vNext. This will not give us support for the new CoreCLR – but we also have a plan how to tackle that.
If you want to try it out yourself – the code can be found here.
Update: two hours later, Christian got everything also running on Ubuntu!
Some of our users already found out and broke the news – so here’s my official post ;)
Beta 3 has been released to github and nuget – 107 commits since Beta 2-1…new features include:
- Anti-forgery token support
- Permission self-service page for users
- Added support to add all claims of a user to a token (and support for implementation specific claims rules)
- Added more documentation and comments
- Added token handle and authorization code hashing
- New view system and support for file system based assets
- Support for WS-Federation, OpenID Connect and social external IdPs
- Support for upstream federated sign-out
- Added flag to hide scopes from discovery document
- Re-worked claims filtering and normalization
- Added support for more authentication scenarios, e.g. client certificates
Documentation will be updated, and new samples will be added ASAP – bear with us.
Again a massive thanks to all contributors and the people giving feedback and filing issues – you make IdentityServer better every day!
One frequently requested feature was the ability to redirect back to the client after logging out of IdentityServer. The session management spec describes this in the “RP-initiated logout” section.
While this is a nice convenience feature and seems trivial to implement, there are some security concerns around the validation of the URL to redirect to after logout is done. This feature could be abused for phishing.
The client first has to prove that it is a legitimate client by sending the original identity token that it received back to the logout endpoint. Furthermore you can now register a list of valid redirect URIs for each client. The request looks like this:
How do you preserve the id_token? You need to store it somehow – e.g. using in the authentication cookie during SecurityTokenValidated notification when using the Katana OIDC middleware. You can then use the RedirectToIdentityProvider notification to attach it back on logout:
RedirectToIdentityProvider = async n =>
// if signing out, add the id_token_hint
if (n.ProtocolMessage.RequestType ==
var idTokenHint =
n.ProtocolMessage.IdTokenHint = idTokenHint;
There are various ways how you can specify the post logout redirect URI – through the above event handler, statically on the OpenIdConnectAuthenticationOptions, or via the RedirectUri property on the AuthenticationProperties when calling IAuthenticationManager.SignOut.
See this sample here. HTH.
We just did a minor update to Beta 2.
Besides some smaller changes and bug fixes we now support redirecting back to a client after logout (very requested feature). I will write a blog post soon describing how it works.
Last night I started working on a getting started tutorial for IdentityServer v3 – while writing it, it became clear, that a single walkthrough will definitely not be enough to show the various options you have – anyways I started with the canonical “authentication for MVC scenario”, and it is work in progress.
Watch this space: