Getting Started with .NET Core Identity Server 4

Configure IdentityServer in startup using dependency injection, add developer signing credentials, and define in-memory API resources and clients, then wire the IdentityServer into the request pipeline.

Set up a config class to define API resources and clients for identity server, enabling resource access and client credentials with hashed secrets and scoped APIs.

Learn how to consume identity server in a .net core client by discovering endpoints, creating a token client, and requesting a client credentials token for bank of dot net api.

Explore the BankOfDotNet solution file contents as part of getting started with identity server; access the full solution zip in lecture resources and look out for bonus lectures.

Install built-in templates to quickly set up a UI-based identity server for the implicit flow. Create an MVC-based client configured for identity server authentication, including login and redirect.

Configure identity server ui assets by setting up the startup file, register static files and html and javascript through the dependency injection pipeline, and enable MVC with the default route.

Add a secure action in the home controller and protect it with the authorize attribute, then create a secure view that lists the user’s claims by looping through them.

Test the mvc client by starting identity server first, launching the client, and completing login and consent to access the secure home page via implicit flow.

Implement the logout action by adding an async logout method that signs out the cookies-based authentication and the OpenID Connect session, demonstrating the login/logout flow with Identity Server 4.

Initialize the identity server database by applying migrations, seed clients, identity resources, and API resources from the config file, using configuration and db contexts and saving changes.