
                    For identityserver4, we pick up the best solutions provided by github life savers.
                    If google brings you here, you are so lucky! These life savers are angels, they have well solved your problems.
                    So do not waste time scrolling the original issue threads just to dig out solutions... 
                    Here you are, you are welcome. Then, go back to work!
                    

I managed to replace the whole authentication handling mechanism and figured out what was happening 

IdentityServer4 Unauthorized (401) during websocket handshake when authorizing SignalR client with JWT bearer token

So I just almost figured this out for using nginx as a reverse proxy But instead of getting https i get http urls in my discovery document 

IdentityServer4 Deploying behind a reverse proxy

When a malformed JWT is passed to a .NET Core 2.0 API using IdentityServer Authentication and a 500 status code is returned instead of a 401 

IdentityServer4 You must either set Authority or IntrospectionEndpoint

@aduggleby: I suspect that some of your users are arrive at the log in screen become distracted and then come back and try to log in more than 15 minute later 

IdentityServer4 Correlation failed at signin-oidc redirect

That worked!
But instead of changing it in the controller I added the following to the Startup.cs file from: 