-
Notifications
You must be signed in to change notification settings - Fork 190
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
Can visit atlantis webpage directly without providing credentials when basic auth credentials are defined in helm chart #113
Comments
@lkysow is there someone I could talk to on the project for a resolution to this? Having this page publicly accessible prevents us from using Atlantis at all. |
:tumbleweed: |
@NathanielWroblewski I guess you figured out but updating to |
Sorry @NathanielWroblewski. This repo isn't checked as frequently. The main Atlantis repo is a better place for issues like this that aren't specific to the Helm chart. Based on @gmontanola's comment I'll close this. |
I'm following the guide for deploying atlantis via helm charts, and I've set
basicAuth.username
andbasicAuth.password
; however, when I deploy to our EKS cluster, I can visit the application page in my browser without being prompted for username/password, and I cancurl
it without being prompted to auth as well.I've added the following to the
values.yml
(I'm omitting everything I haven't altered):Currently, I'm just running this manually and setting the env vars directly on the command line:
I can see that these values are being set:
I have amended my load balancer (ELB) in AWS with an ACM cert, and I'm able to load the Atlantis page over HTTPS, but I am never prompted to enter a username or password.
The text was updated successfully, but these errors were encountered: