-
Notifications
You must be signed in to change notification settings - Fork 1.8k
bug 1633137 request header changes #12998
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
|
The preview will be availble shortly at:
|
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.
| copied to the *_/etc/origin/master/<identity_provider_name>_ca.crt_* file. The | |
| copied to the *_/etc/origin/master/<identity_provider_name>_<identity_provider_type>_ca.crt_* file. The |
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.
| identity provider name is `ldap`, `openid`, or `request_header` to match the | |
| identity provider name is name of the item in `openshift_master_identity_providers` list and identity provider type is `ldap`, `openid`, or `request_header` to match the |
In openshift_master_identity_providers two or more identity providers can be specified:
openshift_master_identity_providers:
- name: foo
provider:
kind: OpenIDIdentityProvider
- name: bar
provider:
kind: OpenIDIdentityProvider
- name: baz
provider:
kind: RequestHeaderIdentityProvider
This config would require the following files:
/etc/origin/master/foo_openid_ca.crt/etc/origin/master/bar_openid_ca.crt/etc/origin/master/baz_requestheader_ca.crt
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.
@enj, are you ready for us to tell people that you can use multiple identity providers?
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.
Mo says that you've always been able to do this.
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 no longer correct, CA certificate location in openshift_master_identity_providers parameter is now ignored
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.
In LDAP insecure option would allow omitting openshift_master_ldap_ca or openshift_master_ldap_ca_file, this doesn't affect other identity providers
|
Looks good, one last change would be removing |
|
@vrutkovs, I've pulled it. Thanks! |
vrutkovs
left a comment
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.
LGTM
|
@stuartchuan Will review from QE. |
|
The changes are OK. |
|
Thank you both! I'll squash and merge after I get a peer review. :) |
|
@openshift/team-documentation PTAL |
|
@kalexand-rh LGTM! |
35a27a5 to
77f7d16
Compare
|
/cherrypick enterprise-3.11 |
|
/cherrypick enterprise-3.10 |
|
@kalexand-rh: new pull request created: #13007 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@kalexand-rh: new pull request created: #13008 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
From https://bugzilla.redhat.com/show_bug.cgi?id=1633137
@vrutkovs, will you PTAL? The bug mentions the
insecureoption. Does #12631 cover what you were thinking?