In Part - 5 of this series you learned to stored IdentityServer configuration data such as identity resources, API resources, and clients into a SQL Server database. However, our sample application still uses TestUser objects to sign into the system. As you would have guessed, in a more real-world app you would like to rope in ASP.NET Core Identity to perform membership tasks. In such a case, instead of using TestUsers you would have IdentityUsers (or its subclass). Let's see how this can be accomplished in this concluding part of this series.