I have a dev instance created and using an IdentityServer3 based server to talk to it. When I click on a protected resource in my client application, the logs show that the ID3 code retrieves the well-known configuration from the dev instance and then tries to retrieve the jwks_uri (oauth2/v1/keys). This always returns a 500 status code and stop processing in my server. What may be going on in my dev instance to do this? Thanks.
Is the 500 error generated on Okta’s end? If yes, can you please provide the full URL in order to check this out?