-
-
Notifications
You must be signed in to change notification settings - Fork 867
Closed
Labels
Description
Hi there!
Please pick the appropriate section (Feature Request or Bug Report) and delete the rest of this. Note that "missing support for X" is a feature request, not a bug!
Feature Request
What challenge are you facing?
Silent/unclear failure on fly login attempt
When running:
fly -t ci login -c http://myurl.ci
fly -t ci set-team --team-name mr-test --basic-auth-username mr --basic-auth-password mr
fly -t ci login -c http://myurl.ci
logging in to team 'main'
username: concourse
password:
target saved
$ fly -t ci set-team --team-name mr-test-2 --basic-auth-username mr --basic-auth-password mr
Team Name: mr-test-2
Basic Auth: enabled
Bitbucket Cloud Auth: disabled
Bitbucket Server Auth: disabled
GitHub Auth: disabled
GitLab Auth: disabled
UAA Auth: disabled
Generic OAuth: disabled
apply configuration? [yN]: y
error: Unexpected Response
Status: 405 Method Not Allowed
Body:
Method Not Allowed
Instead I should run (note the https vs http):
fly -t ci login -c https://myurl.ci
fly -t ci set-team --team-name mr-test --basic-auth-username mr --basic-auth-password mr
fly -t ci login -c https://myurl.ci
logging in to team 'main'
username: concourse
password:
target saved
$ fly -t ci set-team --team-name mr-test --basic-auth-username mr --basic-auth-password mr
Team Name: mr-test
Basic Auth: enabled
Bitbucket Cloud Auth: disabled
Bitbucket Server Auth: disabled
GitHub Auth: disabled
GitLab Auth: disabled
UAA Auth: disabled
Generic OAuth: disabled
apply configuration? [yN]: y
team created
A Modest Proposal
It's not immediately clear to me whether or not the login cmd ought to fail, or if its appropriate for it to return as if it were successful, and then fail on the create team. As a new naive user it appears that the login cmd is failing silently.
AndreasChristianson