-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load ProviderInformation from .well-known/openid-configuration #408
Comments
Yes, that's how it works by default. You just need to set the I feel like there's some confusion somewhere (by one of us), so if I'm not understanding the issue, please let us know. |
Thanks for answering Yes, the problem is on my side. oidcclient throwed an "malformed endpoint" exception, but I don't understand what's wrong and what end point it is. Perhaps you could correct the exception text by indicating what exactly the library does not like in the openid-configuration? Perhaps you can see the error from the json screenshot (first message) the exception is thrown when I don't specify ProviderInformation |
I'm not sure what the issue is, but I have a guess that something that's not JSON is returned. This is likely due to that endpoint returning HTML... perhaps due to an error page being shown? The protocol expects JSON from the endpoint. |
Hello -- any update on this issue? |
How can set EndPoints in ProviderInformation without explicitly specifying it? They are provided in .well-known/openid-configuration.
Can the library take these settings from a openid-configuration endpoint?
I get an exception that endpoints are not specified if I don't explicitly specify them
The text was updated successfully, but these errors were encountered: