Changes for page Create HTTP Access Token for git usage
Last modified by Boris Folgmann on 2026/02/03 13:06
From version 2.4
edited by Boris Folgmann
on 2026/02/03 12:06
on 2026/02/03 12:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Create HTTP Access Token for project or repositoryaccess1 +Create HTTP Access Token for git usage - Content
-
... ... @@ -1,10 +1,11 @@ 1 - TheDevOpsPortalallows youtocreatetechnicalusersonBitbuckettowhichyou can assign roles indifferent projects.The disadvantage is, thatoneBitubucketlicense will be occupied bythis technicaluser.Therefore,as an alternativeconsidercreatingaHTTP Access Token.It'ssuitableifaccesspermissionsfora singleprojectaresufficient. It'salsovery suitableif youareexplicitlyinterestedinlimitingtheaccesstoa singlegit repository.1 +Due to security reasons, you cannot use your password inside a git client when you connect to Bitbucket. Instead, you have to use an HTTP Access Token. To generate one, log in to the DevOps Portal and click "HTTP Access Tokens" in the Bitbucket tile of the dashboard. See screenshot below: 2 2 3 - To createsuch a HTTP access token opne thesettings of the Bitbucket project or repository. In the Security section click on"HTTP access tokens".The pagewill look like shown inthe screenshot below.3 +[[image:1723636654762-377.png||height="197" width="393"]] 4 4 5 -[[ima ge:1770120158545-447.png]]5 +The vendor documentation well describes [[How to create HTTP access tokens on Bitbucket>>url:https://confluence.atlassian.com/bitbucketserver089/http-access-tokens-1236435579.html]], but does not specify which Project and Repository permissions should be chosen for git clients. 6 6 7 +Normal git clients will not interact with the proprietary APIs of Bitbucket, e.g. for handling pull-requests. Instead, git clients just use the standardized git protocol for actions like git clone, pull, and push. The recommended settings for an HTTP access token following the least-privilege principle are: 7 7 8 - Nowclickon "Createtoken"andcreatethetokenwiththerequired permissions.9 +//Project read// and //Repository write//. See the following screenshot: 9 9 10 - To use the token for communicatingwithBitbucket for automationtasks,user the fixedusern11 +[[image:1718784695894-646.png||height="586" width="526"]]
- 1770120158545-447.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -xwiki:XWiki.borisfolgmannt-systemscom - Size
-
... ... @@ -1,1 +1,0 @@ 1 -91.7 KB - Content