Adds support for error page in Client Certificate Authentication #1293
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
k8s-ci-robot
added
the
cncf-cla: yes
|
This change is |
k8s-ci-robot
added
the
size/M
|
@jcmoraisjr Please take a look, this can be useful also to HAProxy Ingress Controller. |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
@rikatz thanks! |
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 error handling in Client Certificate Authentication.
When user doesn't presents a valid certificate, he can be redirected to another page/URL instead of receiving a 400 error.
This must be a different location than the authenticated page, as an example:
If the used doesn't present a certificate, the redirect must be done to something like nocert.mysite.com, with a valid error page/location.