Open nabadger opened 4 years ago
It looks like Move from coreos/go-oidc OAuth2 library to golang.org/x/oauth2
doesn't work with skip-openid-provider-tls-verify
config.
@jangaraj I think it's not passing in the desired context here
https://github.com/louketo/louketo-proxy/blob/master/oauth.go#L134
The provided context is what can be used to control which http-client is used. Suspect it's using a default one.
Also wondering if there might have been some confusion here:
https://github.com/louketo/louketo-proxy/blob/master/oauth.go#L94
Args suggest it's passing through the oidc-client, but it's actually the config.
Hi, is there a workaround for this issue?
Workaround: make CA cert available for Louketo (it must be available in the /etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
in case of louketo Docker image)
I would also really appreciate a fix for this, I guess it is not really hard if you have some go knowledge and know the sources of this project which I currently not really have, there is also an example https://github.com/golang/oauth2/issues/187#issuecomment-227811477 I will take a look at this when I find some time.
Edit: just saw the pinned issue regarding sunsetting the project, totally missed that...
See https://github.com/jangaraj/louketo-proxy/commit/ddb37f62388fbd046ec6cb181ef73a9d32826903 feel free to test and create here.
Title
x509: certificate signed by unknown authority (1.0.0)
Summary
I'm finding that since switching from
quay.io/keycloak/keycloak-gatekeeper:10.0.0
tolouketo/louketo-proxy:1.0.0
I get 403 errors when attempting to auth.Reverting to
gatekeeper:10.0.0
works.There are no other configuration changes happening here (just the image).
Environment
Version of everything that it's running in your environment:
Configuration
I'm specifying both
skip-upstream-tls-verify
andskip-openid-provider-tls-verify
Expected Results
Token issued, auth'd and redirected to upstream site, i.e:
Actual Results
Louketo logs: