Quote from Eben Monney on March 16, 2018, 7:45 am

No those two are not related.

It'll be helpful if you provided the complete error stack than only the top level error. The inner errors mostly contain the actual trigger.

To debug I would start with the following:

1. Try navigating to http://localhost:50314/.well-known/openid-configuration from the browser and see if that endpoint is up. If you don't get a response crosscheck the address and port configuration in IdentityServer's configuration (see .AddIdentityServerAuthentication() options in Startup.cs)
2. This can also be a security/certificate issue. Are you using the AddDeveloperSigningCredential? (You can check this from Startup.ConfigureServices method). If you have a different certificate configured crosscheck the validity

You can post the complete error message here or send to a mail: support@ebenmonney.com for further assistance.

Also to use SQLServer to save IdentityServer's data rather than have it in memeory please refer to this blog post: https://www.staging8.ebenmonney.com/configure-identityserver-to-use-entityframework-for-storage/.

This will satisfy this notification " You are using the in-memory version of the persisted grant store. This will store consent decisions, authorization codes, refresh and reference tokens in memory only. If you are using any of those features in production, you want to switch to a different store implementation."

Quote from Al Ve on April 1, 2018, 12:02 pm

for others who might get that too, check your startup class and point your authority to the correct localhost for dev environment. In the case above it should be ->

services.AddAuthentication(IdentityServerAuthenticationDefaults.AuthenticationScheme)
.AddIdentityServerAuthentication(options =>
{
options.Authority = "http://localhost:50314/";