Concourse Login Issues
geofffranks opened this issue · 10 comments
I'm trying to integrate concourse-summary with a concourse that has pipelines which are not publicly available. I tried adding the ?login_form param to the end of the URL for the concourse, in the HOSTS env var on the app. This triggers concourse-summary to pop up an authentication form, but when I put in the username/password, I still don't see any pipeline data.
TCP dumping on my concourse node shows no evidence of an Auth header, or the /api/v1/teams/#{team_name}/auth/token call occurring. Any ideas what i'm doing wrong?
Looks like there might be some caching involved that prevented me from seeing the auth request. I caught another tcp dump of it in there. However, the ATC-Authorization cookie being set isn't being passed back to concourse for the pipeline retrieval calls (Concourse version 3.3.2)
At the moment concourse summary auth with username/password, is that what you are using, or are you using github auth (or other)?
I personally only use a publicly accessible concourse server so I don't notice if APIs for auth change.
We have both github + basic auth set up on this concourse. I was attempting to use basic auth for concourse-summary
OK. Thanks for the confirmation, I'll try and work this out
Hi @geofffranks I just checked against buildpacks.ci.cf-app.com which is on concourse 3.3.4 and used http://concourse-summary-crystal.cfapps.io/host/buildpacks.ci.cf-app.com?ignore_groups&login_form and my basic auth to concourse username/password auth worked. Are you still having a problem?
Are you using https://concourse-summary-crystal.cfapps.io/ or your own instance of concourse summary? If you are using your own, would you mind trying to use https://concourse-summary-crystal.cfapps.io/ and see if it has the same problems?
Are you able to give me access to your concourse deploy through some direct channel (eg. dave@goddard.id.au)
probably not. we'll just use it with the publicly viewable pipelines instead