Closed piontec closed 8 years ago
I'm able to replicate this. It looks like basic auth on the reverse proxy is causing the issue. If I disable auth on the proxy (change ENABLE_BASIC_AUTH
to false
in ssl_proxy.yaml
, Jenkins authentication works. The proxy authN was intended to provide basic protections until the user configures Jenkins auth, so this seems like the right thing to do. LMK if that sounds right and I'll close the issue. Thanks!
Hello,
I am experiencing the same problem. Even disabling auth on the proxy, as soon as I click on "save" I am locked out.
Can you share how you setup the configuration please?
Hi @alledm,
I just walked through enabling Jenkins auth and have it working fine. Here's what I did:
kubectl delete -f ssl_proxy.yaml
ssl_proxy.yaml
and change ENABLE_BASIC_AUTH
to false
kubectl delete -f ssl_proxy.yaml
Please let me know if that works and I'll close the issue.
Thanks,
Evan
On clean install, with SSL enabled and default basi auth credentials, you lock out yourself after enabling 'global security'.
To reproduce: 1) configure ssl_secrets.yaml to include cert, key and dh 2) in ssl_proxy.yaml - enable SSL, set to 'true' 3) wait for jenkins 4) in jenkins click:
refresh and basic auth popup with 'Jenkins' realm will appear - no idea what the credentials should be.