Support auth via certificates and headers #343
Conversation
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
|
Thanks for this PR. This means I can use for example mod_auth_openidc for Apache2 to handle authentication. |
|
Can this feature be merged? It would be very useful! |
|
+1 Would love to see this merged to enable "X-Forwarded-User"-Auth via reverse proxy! |
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 adds support for authentication via a client certificate (#300) or via a header set by a reverse proxy.
In order to use a client certificate (or auth by header), the username passed to
docker loginmust match that of the certificate's CN or the value in the header used for authentication. The password doesn't matter. I've added an example to show how I'm using it in theexamplesfolder.