remote: CHANGE-3222 - Functionality has been deprecatedremote: App passwords are deprecated and must be replaced with API tokens.remote: https://developer.atlassian.com/cloud/bitbucket/changelog#CHANGE-3222Tokens are not working, how to fix this?
Hello @taluks
That 410 error means Bitbucket is rejecting your old app password during scheduled brownout.
On July 11, Bitbucket is running scheduled app-password brownouts. During these windows, Git-over-HTTPS requests authenticated with an app password return HTTP 410 and the CHANGE-3222 message.
Switch SourceTree to a User API Token with user, workspace, and repository scopes.
Update your account in SourceTree using your Atlassian email, then clear any old bitbucket.org entries from Windows Credential Manager or macOS Keychain and restart the app. If you skip clearing that credential cache, Git will just keep pushing the dead password in the background.
Cheers,
Arek 🤠
We have never used app passwords, and are getting this error using Access tokens, API tokens, and also getting "user 112 not known" errors using ssh auth during the brownout periods. There does not seem to be any form of git authentication that is working reliably any more.
Bitbucket is unusable, and we are on the verge of switching away to another provider due to this issue, as we are losing productivity because of it.
The user 112 not known message is not the normal Bitbucket SSH authentication response. Check whether an SSH configuration, proxy, wrapper, or URL rewrite is replacing git with another username.
Sorry, you are right, it seems to be a Docker container issue we are running into using ssh URLs from jenkins, the message is the same as: https://unix.stackexchange.com/questions/524268/running-git-or-ssh-client-in-docker-as-user-no-user-exists-for-uid
For now, API tokens seem to be working, and I did some experiments to show we are in fact inside a brownout period now, so whatever we have been experiencing over the past week seems to be fixed for now (fingers crossed).
What I have discovered, and is not obvious from the documentation of this whole deprecation process, is that even using API Tokens or Access Tokens, you will get failures if you are using the Authentication: Basic base64(username:api-token) form of authentication. In addition to using API Tokens, you need to use the Authentication: Bearer api-token form of authentication to avoid any errors when using the API.
username:api-token Basic authentication only seems to work now for git over https using API tokens, not for API usage.
The Bitbucket client always resets its damn token!!!
It looks like you're new here. Sign in or register to get started.
