-
Bug
-
Resolution: Fixed
-
Critical
-
blueocean-plugin, master, 2017-08-15, commit ea1df49
-
-
Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2
If a user registered a Bitbucket Cloud credential with Blue Ocean and then later changes their Bitbucket / Atlassian password, they receive an opaque error message with no obvious way to fix it.
Repro Steps
- Click "New Pipeline" from Blue Ocean dashboard
- Click "Bitbucket Cloud"
- Enter a valid user name and password
- Note: credential is saved successfully and user is prompted to choose a team.
- Open a new tab and navigate to Bitbucket or Atlassian account manager and change the password.
- Click "Bitbucket Cloud" again (to relaunch the flow)
Expected Behavior
- User should see the credential step with an error message indicating the stored credential is no longer valid.
Actual Behavior
- User received "Unauthorized" error message
Workaround
- User must enter classic, open their credentials listing and delete their "bitbucket-cloud" credential, then relaunch the creation flow
Notes
- I believe this also affects Bitbucket Server.
- I don't believe this is a regression but rather a defect in the original implementation.
- This kind of "credential revalidating" behavior is implemented in GitHub and GitHub Enterprise. AbstractBitbucketScm.getState just needs to add some logic to validate the existing credential again.
- links to