Last modified by Boris Folgmann on 2026/02/03 14:36

Hide last authors
Boris Folgmann 5.1 1 The DevOps Portal allows you to create technical users on Bitbucket to which you can assign roles in different projects. The disadvantage is, that one Bitubucket license will be occupied by this technical user. Therefore, as an alternative consider creating an HTTP access token. It's suitable if access permissions for a single project are sufficient. It's also very suitable if you are explicitly interested in limiting the access to a single git repository.
Boris Folgmann 1.2 2
Boris Folgmann 5.1 3 To create such an HTTP access token open the settings of the Bitbucket project or repository. In the Security section click on "HTTP access tokens". The page will look like shown in the screenshot below.
Boris Folgmann 1.2 4
Boris Folgmann 8.1 5 (% aria-label="1770120158545-447.png image widget" contenteditable="false" role="region" style="background:rgba(220, 220, 220, 0.5) url(~"https://prd.sdc.t-systems.net/xwiki/webjars/wiki%3Adevopsaas/xwiki-platform-ckeditor-webjar/16.10.14/plugins/widget/images/handle.png~"); left:0px; top:-15px" tabindex="-1" %)[[image:1770123885637-291.png||data-xwiki-image-style-border="true" height="509" width="1010"]]
Boris Folgmann 1.3 6
Boris Folgmann 5.1 7 Now click on "Create token" and create the token with the required permissions.
Boris Folgmann 1.3 8
Boris Folgmann 5.1 9 To use the token for communicating with Bitbucket for automation tasks make sure to authenticate like this:
10
11 * Username: "x-token-auth" (static text)
12 * Password: value of the access token
13
Boris Folgmann 8.2 14 [[DevOps Portal 2.2.0>>Blog.DevOps Portal 2\.2\.0]] and later uses the same approach to allow Jenkins to retrieve the source codes from Bitbucket projects.
Boris Folgmann 5.1 15
16
17