When using SQL Server to maintain your configuration and operational store for IdentityServer4, it’s fairly simple to tell IdentityServer to use a specific custom schema and custom table names. The process is similar to the way one configures ASP.NET Core Identity to use custom table names.
ASP.NET Core Identity is a very useful tool which provides a simple interface for user management. The default out-of-the-box implementation involves using Microsoft’s default table names and using a string (which defaults to a guid) for primary keys. If you don’t like these defaults it’s fairly simple to change the table names and schema and to use an auto-incrementing integer as a primary key.
The private NuGet package feed included with Visual Studio Team Services provides a straightforward way to distribute proprietary NuGet libraries for use by multiple .NET applications within your organization without publishing your sensitive proprietary library publicly over the internet for all to use. Microsoft provides good documentation for how to do this in Windows, but I had to do some digging and troubleshooting in order to get it working in Linux. Once you figure it out it’s fairly simple, but…