Microsoft released ASP.NET Core 3.0 a few weeks ago, which means breaking changes for everyone! You’ll have to rewrite your Configure method to handle the new routing and authorization middleware and update your site to handle your preferred flavor of controllers and UI. IdentityServer4, itself, also jumped to a new major version (v3.0) and moved from .NET Standard 2.1 to .NET Core App 3.0.
However, you will be pleased to know that there are no breaking changes for the IdentityServer4 commercial components. Our products are now multi-targeting .NET Standard 2.0 and .NET Core 3.0, using a single codebase.
We have also updated any supporting Entity Framework storage libraries to support both Entity Framework Core 2.x and 3.0.
SAML 2.0, WS-Federation, and Dynamic Authentication Providers
These components have all had a minor version update and are currently available as pre-releases. Your usual demo and production license keys will work out of the box.
ASP.NET Core 3.0 support is available in the following versions upwards:
FIDO2 for ASP.NET Core
FIDO2 has also moved a minor version. We had to update our quickstart guide for this one due to the new JSON serializers in ASP.NET Core 3.0 not supporting entities without parameterless constructors.
You can find DTOs for Base64 and Base64 URL encoded authenticator responses in the Rsk.AspNetCore.Fido.Dtos
namespace. Just be sure to call ToFidoResponse
before passing them to our component.
AdminUI
AdminUI itself is not going to use ASP.NET Core 3.0 but instead remain on ASP.NET Core 2.1, which has Long-Term Support (LTS) from Microsoft. However, next year, we do plan on moving to ASP.NET Core 3.1, which will be Microsoft’s LTS version for 3.x.
Since IdentityServer4 v3.0 does not contain any database-level breaking changes, AdminUI can safely continue to use ASP.NET Core 2.1.
For our supporting libraries, we have updated these to also multi-target:
Feedback
If you experience any issues with these updates, let us know by emailing [email protected].
If you have already been trying our previews, please ensure that you are using the versions listed above, as opposed to 3.x preview versions (we backed out of the major version change).