Access Token Error After Push to Bitbucket

[Geary Sutterfield]

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. 

[Stephen Sifers]

Hello Geary and welcome to the Community!

Thanks for providing details into the issues you’re running into when attempting to Commit to Bitbucket. To understand a bit more on this, could you please clarify the following for us:

• Could you let us know which product this log entry is coming from?

This would allow us to see which side is having an issue communicating with which and a better look into the issue.

We look forward to hearing back.

Regards,
Stephen SIfers

[Geary Sutterfield]

Stephen - Thanks for the reply. The log entry is on the Bitbucket side. Here's the entire log record:

2019-08-26 17:44:52,437 WARN  [http-nio-8080-exec-9] glsutter @HKMI57x1064x15253x2 1cvs5v2 192.80.55.87 "GET /rest/applinks/3.0/status/c9ccc5e4-ac88-3ebe-866a-76a69cb758cf HTTP/1.1" c.a.a.i.m.remote.TryWithCredentials You do not have an authorized access token for the remote resource.

Some further info - I can use the Application Links pull down "Go to remote" from Bitbucket to Bamboo, but when I click on the Edit icon on the Bitbucket side, I see the above error in the log. Although it still shows green status and Connected. 

Both servers are running on an AWS EC2 instance in the same VPC. There's a proxy server involved for outbound requests, but I've configured the JVM variables and both servers are in the nonProxyHosts. I don't believe that should affect this communication. And, as I mentioned, I can use the "Go to remote" pull down in both directions w/o any problems. 

Thanks for any insight into how to proceed. 

Geary

[Stephen Sifers]

Hello Geary,

Thanks for the clarification on where that log comes from and the additional information. I’m not finding anything very clear on this error which is leading me to ask if you’re using any 3rd party OAuth provider or possibly scriptrunner within Bitbucket?

This will help clarify where exactly this error is coming from.

Regards,
Stephen Sifers

[Geary Sutterfield]

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

[Stephen Sifers]

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]

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.