The information below applies to repositories on Bitbucket Server, but only if you use the hub workflow features to submit for review or review change requests.


Personal access tokens

If you don't have a valid Personal Token, you may get the error message below, indicating that your token has passed its expiration date, or that it does not have the right permissions enabled.



In the repository connection manager, click on the "generate" link located to the right of the input field for the personal access token. You can find more information on how to generate a personal access token in the Bitbucket Server documentation.


Workgroup - manage hub connections - Bitbucke



Clicking on the "generate" link brings you to the Bitbucket Server form.  Note that, in terms of permissions, Hackolade Studio requires at minimum the "repository write" permission in order to be able to perform Pull Requests actions.

Workgroup - Bitbucket personal token


If you don't have sufficient rights to issue tokens, you may have to request one from your administrator.  


To re-issue an expired token, proceed like creating a new one, then:

  • navigate to your list of personal access tokens on Bitbucket Server;
  • click on the Create Token button in order to create a new token;
  • edit the connection in Hackolade, as described above, and copy-paste the new token from Bitbucket Server.



Username and Password

Alternatively, you may use your account username and password, but it is typically discouraged for security reasons. With a token, if an external system is compromised, you simply revoke the token instead of changing password, and consequently changing it in all scripts and integrations. It is recommended you only map one token per integration, then If the integrated system is compromised, you can remove that token and not affect any of the other integrations.


In the repository connection manager, select Connect with Username and Password and enter your credentials.

Workgroup - Bitbucket basic auth