allow to use local file through file:// protocol for metadata or jwks #51
Conversation
This file contains 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
|
for completeness: there's overlapping functionality through |
zandbelt
added a commit
that referenced
this pull request
Jun 24, 2024
Signed-off-by: Hans Zandbelt <hans.zandbelt@openidc.com>
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.
This PR to allow usage of file:// protocol in various options so as to put key files or metadata on local storage rather than depending upon network.
It is useful in use-case where HTTP server is denied to connect to external services as it is the default on some OS with SELinux enabled (ie RHEL).
For example :
OAuth2TokenVerify $source_token jwks_uri file:///etc/nginx/my_jwks.json ;