Draft
Conversation
67cab5f to
34717c9
Compare
7f508d5 to
59d14f0
Compare
59d14f0 to
e8a6910
Compare
984f986 to
2aa204f
Compare
Collaborator
Author
|
|
c894c0d to
f263f23
Compare
78c96a8 to
3c82c72
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
OIDC endpoints are best set via the discovery mechanism rather than hard-coding paths. This is not supported by
oauth2, but a smaller library on top by the same author,openidconnectdoes support it. Currently it's quite verbose to code this due to the API, but bothoauth2andopenidconenctare due a new major release quite soon, so will return to this after that is out.