Azure Key Vault is a great way to store your IdentityServer4 signing keys; it is secure, versioned, and gives you access to robust access control mechanisms. However, I keep seeing many Azure Key Vault integrations that miss many of its features by storing the private key as a secret and then downloading the private key on application startup.

In this article, we will see how we can skip Identity server 4 login page if we have integrated Azure AD with identity server 4.

This repository contains demo projects for IdentityServer4. To learn how to create these projects yourself you can use my zero to production-ready step-by-step tutorials and client app examples.

This article shows two possible ways of getting user claims in an ASP.NET Core application which uses an IdentityServer4 service. Both ways have advantages and require setting different code configurations in both applications.

This article shows how FIDO2 WebAuthn could be used for a passwordless sign in integrated into an ASP.NET Core Identity application. The FIDO2 WebAuthn is implemented using the fido2-net-lib Nuget package, and demo code created by Anders Åberg. The application is implemented using ASP.NET Core 3.0 with Identity. For information about FIDO2 and WebAuthn, please refer to the links at the bottom.

Building an Identity Server for authentication and authorization is quite straightforward. You can easily find a tutorial for this then install the required packages, copy-paste-modify some line of codes and congratulations! You’re done.

The administration for the IdentityServer4 and Asp.Net Core Identity

Jp Project is an Open Source UI Administration Tools for IdentityServer4 v2 - release 2.4.0.

Do you have an Identity server 4 project? Are you looking into delegating user permissions? Have you seen how Google Service accounts work and need to work out something similar in Identity server 4. Well this tutorial should help.

Series of post on identity server