Access Token Error After Push to Bitbucket

Question

Getting this error in the log when pushing a commit to Bitbucket:

c.a.a.i.m.remote.TryWithCredentials You do not have an authorized access token for the remote resource.

We have self-hosted Bitbucket and Bamboo servers. Followed all the instructions for setting up Application Links between the two servers. And from Application Links page on both servers, it says Connected (Green) and we can use the "Go to remote" pulldown without any problem.

The plan configuration looks okay, AFAIK:

- "Bitbucket Server repository triggered" is save as trigger

- The plan is enabled

- Under Repositories in the Plan, the Bitbucket repo is shown as a Linked Repository,

We have also tried re-creating the links between Bitbucket and Bamboo several times in different ways - Some without saying we're admin on both, and some saying we are. Creating the links when creating the first plan, and creating the links before creating a plan.

Still, when a commit is pushed to the Bitbucket repo, we get the access token error in the Bitbucket log. Obviously, Bitbucket is not notifying Bamboo when the change is made.

Any ideas on how to resolve this problem? Thanks.

Geary Sutterfield · Answer

Hey Stephen:

I found the problem. Doesn't seem to be related to the "You do not have an authorized access token" in the log. I didn't have the Branches configured correctly in the Plan. Simple explanation - I thought Automatic Branch Management would detect existing branches, but looks like it only detects NEW branches or pull requests.

The log message still might be worth looking into. But my work is no longer being held up.

Thanks for your help.

Stephen Sifers · Answer

Hello Geary,

I'm going to move this issue to the support queue and create a support request on your behalf for this issue. For the next steps you'll receive an email confirming we've created a case, I'll ask you to please create a support zip and attach it to the case I'm creating.

Here are the instructions on how to create a support zip: Create a Support Zip

Regards,
Stephen Sifers

Geary Sutterfield · Answer

I haven't been able to find anything, either. We're creating internal users on Bitbucket and Bamboo. Not using any 3rd party OAuth providers. The Application Links are both set to simple OAuth (no impersonation).

I wanted to set the log level to DEBUG for that Java class, but I couldn't find a full class name anywhere. Any idea of the full class name for c.a.a.i.m.remote?

Thanks,

Geary