The official documentation for these Identity Server 4 quickstarts can be found on the official website. The goal of these is to provide step by step instructions for various common IdentityServer scenarios.
The purpose of this repository is to track my implementation of these quickstarts while I follow the official documentation. Thus, it is recommended that readers refer to the official documentation for a more complete picture of the inner workings of Identity Server 4.
This first quickstart is the most basic scenario for protecting APIs using IdentityServer. Here we define an API and a Client with which to access it. The client requests an access token from the Identity Server using its client ID and secret and then uses the token to gain access to the API.
This quickstart focusses on adding support for interactive user authentication via the OpenID Connect protocol to our IdentityServer. Once that's in place, we create an MVC application that uses IdentityServer for authentication.
In this quickstart we will explore combining API access and user authentication.
This quckstart demonstrates how to build a JavaScript client, otherwise know as a "Single Page Application" (or "SPA").
Through this client the user will login to IdentityServer, invoke the web API with an access token issued by IdentityServer, and logout of IdentityServer.
The goal of this quickstart is to move our data into a database that is persistent between restarts and across multiple IdentityServer instances. This includes configuration data, such as client and scope data, as well as IDS4 temporary data, such as authorization codes, consent choices, and refresh tokens.
This quickstart shows how to use ASP.NET Core Identity with IdentityServer.