You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/administration/user-self-management/manage-pats.md
+23-19Lines changed: 23 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,9 +5,7 @@ group: administration
5
5
toc:true
6
6
---
7
7
8
-
9
-
10
-
8
+
##Git user token management
11
9
As a user in Codefresh, you must authorize access to your Git provider accounts and authenticate Git-based actions from Codefresh clients, per provisioned GitOps Runtime. This is done through the Git user token, which is an access token unique to each user. For more details, including required scopes and how the Git user token differs from the Git Runtime token, see[Git tokens in Codefresh]({{site.baseurl}}/docs/security/git-tokens/).
12
10
13
11
@@ -28,16 +26,21 @@ If you have access to more than one GitOps Runtime in the same or in different a
28
26
>**NOTE**
29
27
For OAuth2, the administrator pre-configures the permissions and expiry date. Once you supply your credentials for authorization, you are automatically directed to the Git Personal Tokens page.
30
28
31
-
**Before you begin**
32
-
29
+
#####Before you begin
30
+
{% if page.collection != site.gitops_collection %}
33
31
Make sure you have:
34
32
* For Bitbucket only, your Bitbucket account username
35
-
* If needed, a_user access token_ from your Git provider with the required scopes
33
+
* If needed, a_user access token_ from your Git provider with the required scopes: