-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
fix: OAuth2 callback with self-signed Root CA. Fixes #6793 #6978
Conversation
Signed-off-by: Niclas Schnickmann <niclas.schnickmann@nextstep-services.de>
Codecov Report
@@ Coverage Diff @@
## master #6978 +/- ##
==========================================
- Coverage 48.52% 48.50% -0.02%
==========================================
Files 265 265
Lines 19272 19273 +1
==========================================
- Hits 9352 9349 -3
- Misses 8867 8868 +1
- Partials 1053 1056 +3
Continue to review full report at Codecov.
|
Please comment if your changes are in v3.2 and we need to backport this. |
Thanks for merging. If I get you correctly (just let me know if not) then no. The branch containing my changes was based on master branch and not release-3.2. |
…rgoproj#6978) Signed-off-by: Niclas Schnickmann <niclas.schnickmann@nextstep-services.de> Signed-off-by: kriti-sc <kathuriakriti1@gmail.com>
@NextNiclas @alexec I think we should also add a config to specify a custom root CA, (rather than encouraging users to blindly trust all certs). Here is an example config: apiVersion: v1
kind: ConfigMap
metadata:
name: workflow-controller-configmap
namespace: argo
data:
sso: |
...
## `rootCaFile` is just an example name
rootCaFile: "/etc/oauth2-proxy/certs/ca.crt" |
I have raised issue #7198 based on my proposal in: #6978 (comment) |
Signed-off-by: Niclas Schnickmann niclas.schnickmann@nextstep-services.de
Looks like #6961 did not fix #6793 completely as I missed to add an http.Client to the oauth Exchange call.
This one was tested on my staging cluster and works fine with Keycloak (internal CA/self-signed).