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/account-user-management/oauth-setup.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title:"Set up OAuth2 authentication for Git providers"
2
+
title:"Seting up OAuth2 for Git providers"
3
3
description:""
4
4
group:administration
5
5
sub_group:account-user-management
@@ -33,7 +33,7 @@ Codefresh supports OAuth2 or personal access tokens (PATs) for authentication:
33
33
34
34
35
35
36
-
###Authentication for Git providers and runtime accounts
36
+
##Authentication for Git providers and runtime accounts
37
37
The[Authentication](https://g.codefresh.io/2.0/account-settings/authentication?providerName=github){:target="\_blank"} page displays the accounts by Git provider and the authentication method selected for the same.
38
38
39
39
Authentication accounts are organized by Runtimes. A runtime can have a single authentication account.
@@ -51,7 +51,7 @@ The Type column identifies the authentication for the provider account as either
51
51
52
52
As the account administrator, you can change the authentication method for an account at any time to either Codefresh or Custom, or manual token entry. See[Select authentication mechanism for runtime](#select-authentication-mechanism-for-runtime).
53
53
54
-
###Create a custom OAuth2 Application for Git provider
54
+
##Create a custom OAuth2 Application for Git provider
55
55
Create a custom OAuth2 Application for Codefresh in your Git provider accounts with the correct scopes, and set up authentication for the same within Codefresh. Users in Codefresh can then authorize access to the Git provider using OAuth2, instead of a personal access token.
56
56
57
57
Supported Git providers:
@@ -72,7 +72,7 @@ To set up OAuth2 authorization in Codefresh, you must:
72
72
<br>
73
73
{:/}
74
74
75
-
####Step 1: Create a custom OAuth2 Application in Git
75
+
###Step 1: Create a custom OAuth2 Application in Git
76
76
Create and register an OAuth App under your organization to authorize Codefresh.
77
77
78
78
1. Follow the step-by-step instructions for your Git provider:
@@ -112,7 +112,7 @@ Create and register an OAuth App under your organization to authorize Codefresh.
112
112
<br>
113
113
{:/}
114
114
115
-
####Step 2: Create a K8s secret resource in the runtime cluster
115
+
###Step 2: Create a K8s secret resource in the runtime cluster
116
116
Create a K8s secret in the runtime cluster, using the example below as a guideline. You must define the application ID (`appId`), client ID (`clientId`) and the client secret (`clientSecret`) from the OAuth2 Application you created in your Git provider, and the Git URL (`url`).
117
117
118
118
>All fields in the secret_must be_ encoded in`base64`.
@@ -155,7 +155,7 @@ data:
155
155
<br>
156
156
{:/}
157
157
158
-
#### Step 3: Configure OAuth2 settings for Custom Application in Codefresh
158
+
### Step 3: Configure OAuth2 settings for Custom Application in Codefresh
159
159
160
160
Configure the settings for the Custom OAuth2 Application in Codefresh. Configuring the settings creates a K8s ConfigMap that references the OAuth secret credentials. When configuring the settings, you can work in Form mode, or directly update the YAML manifest.
161
161
@@ -211,7 +211,7 @@ Configure the settings for the Custom OAuth2 Application in Codefresh. Configuri
211
211
212
212
You have completed the setup to authorize Codefresh as an OAuth App for your Git provider.
213
213
214
-
### Select authentication mechanism for runtime
214
+
## Select authentication mechanism for runtime
215
215
For a Git provider and a runtime account, select the authentication mechanism:Codefresh account, Custom provider account if one exists, or token-based authentication.
216
216
217
217
1. In the Codefresh UI, go to [Authentication](https://g.codefresh.io/2.0/account-settings/authentication?providerName=github){:target="\_blank"}.
Copy file name to clipboardExpand all lines: _docs/administration/account-user-management/platform-ip-addresses.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ toc: true
9
9
Access to Kubernetes clusters behind strict firewalls not accessible from the public internet is governed through authorized IP addresses.
10
10
Codefresh provides a list of IP addresses to be configured on clusters to allow access to them.
11
11
12
-
You can register multiple external clusters to the Codefresh Runner, and GitOps Runtimes. All Runtimes require Codefresh platform IPs to be configured on the clusters.
12
+
You can register multiple external clusters to the Codefresh Runner and GitOps Runtimes. All Runtimes require Codefresh platform IPs to be configured on the clusters.
13
13
In addition, managed clusters registered to Hosted GitOps Runtimes must be configured with a set of specific IP addresses to authorize access.
14
14
15
15
@@ -39,13 +39,13 @@ All the IPs are NAT gateways, and need to enable specific IPs instead of ranges.
>Note: When configuring the default IDP (for GitHub, GitLab, etc), do not modify the Client Name field. Please keep them as GitHub, GitLab, BitBucket, etc. Otherwise, the signup and login views won’t work.