since version 4.0 (we tested 4.1 too) we are unable to log into our Concourse using the basic auth method.
Bosh cluster deployment using concourse-bosh-deployment
bosh vms -d concourse Deployment 'concourse' Instance Process State AZ IPs VM CID VM Type db/0d48a071-3821-4145-a2ec-82fb09cc279d running z1 172.27.1.31 vm-a9cc448f-22df-4645-8e22-db91d629a50d small web/00abb06c-7491-4fca-b169-5fcfbf5df9f6 running z1 172.27.1.33 vm-c283405e-52bf-44cf-86aa-c7ff00aaa0d6 medium worker/6a00bfb5-a8c9-4aaf-9646-c74448b2243a running z1 172.27.1.34 vm-d2e284aa-3b75-4e48-b9c6-9970496a9ca2 large worker/78345867-1749-4edc-a09c-c90a71ca429e running z1 172.27.1.32 vm-eda36f85-f562-4946-b775-fa95fc7b18de large
Our routing is configured that 18.104.22.168 redirects to 172.27.1.1 which is the standard router for 172.27.1/24.
Our external URL in the concourse manifest is
We added our standard user using the concourse-bosh-deployment ops file https://github.com/concourse/concourse-bosh-deployment/blob/master/cluster/operations/basic-auth.yml.
We can see the home screen of Concourse under
https://22.214.171.124:8080 and a click to login
redirects us to the login form
https://126.96.36.199:8080/sky/issuer/auth/local?req=<req_id> which is also displayed.
When we enter wrong Concourse credentials, the form receives a tooltip that indicates that the credentials are invalid. If we enter valid credentials, our redirect to
https://188.8.131.52:8080/sky/callback?code=<code> receives a HTTP error 400 response.