Changes for page Create HTTP Access Token for git usage

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -5,6 +5,19 @@
5	5	[[image:1770120158545-447.png]]
6	6
7	7
8		-Now click on "Create token" and create the token with the required permissions.
	8	+Now click on "Create token" and create tokne with the required permissions.
9	9
10		-To use the token for communicating with Bitbucket for automation tasks, user the fixed usern
	10	+
	11	+
	12	+
	13	+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:
	14	+
	15	+[[image:1723636654762-377.png||height="197" width="393"]]
	16	+
	17	+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.
	18	+
	19	+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:
	20	+
	21	+//Project read// and //Repository write//. See the following screenshot:
	22	+
	23	+[[image:1718784695894-646.png||height="586" width="526"]]