-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Add cert validation option to requestheader #1246
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Clarify. I think this is wrapping a RequestAuthenticator inside of another RequestAuthenticator that requires a valid client cert as opposed to pulling the user info from a client cert.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the unified glog.Fatal for now
|
@deads2k comments addressed |
|
lgtm [merge] |
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_requests_openshift3/1143/) (Image: devenv-fedora_1007) |
|
Evaluated for origin up to dcf2797 |
Merged by openshift-bot
…vsphere UPSTREAM: 59440: Use SetInformers method to register for Node events
@brenton fyi