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
Once complete, run `sudo service coder restart` to reboot Coder.
48
48
49
-
## OpenID Connect with Google
49
+
## GitLab
50
+
51
+
### Step 1: Configure the OAuth application in your GitLab instance
52
+
53
+
First, [register a GitLab OAuth application](https://docs.gitlab.com/ee/integration/oauth_provider.html). GitLab will ask you for the following parameter:
54
+
55
+
-**Redirect URI**: Set to `https://coder.domain.com/api/v2/users/oidc/callback`
56
+
57
+
### Step 2: Configure Coder with the OpenID Connect credentials
58
+
59
+
Navigate to your Coder host and run the following command to start up the Coder
60
+
server:
61
+
62
+
```console
63
+
coder server --oidc-issuer-url="https://gitlab.com" --oidc-email-domain="your-domain-1,your-domain-2" --oidc-client-id="533...des" --oidc-client-secret="G0CSP...7qSM"
64
+
```
65
+
66
+
Alternatively, if you are running Coder as a system service, you can achieve the
67
+
same result as the command above by adding the following environment variables
If you are using a self-hosted GitLab instance, replace `gitlab.com` in the above URL
88
+
with your internal domain. The same will apply for the `OIDC_ISSUER_URL` variable.
89
+
90
+
## OpenID Connect with Google
52
91
53
92
### Step 1: Configure the OAuth application on Google Cloud
54
93
55
-
First, [register a Google OAuth app](https://support.google.com/cloud/answer/6158849?hl=en). Google will ask you for the following Coder parameters:
94
+
First, [register a Google OAuth application](https://support.google.com/cloud/answer/6158849?hl=en). Google will ask you for the following Coder parameters:
56
95
57
96
-**Authorized JavaScript origins**: Set to your Coder domain (e.g. `https://coder.domain.com`)
58
97
-**Redirect URIs**: Set to `https://coder.domain.com/api/v2/users/oidc/callback`
Once complete, run `sudo service coder restart` to reboot Coder.
81
120
82
-
> When a new user is created, the `preferred_username` claim becomes the username. If this claim is empty, the email address will be stripped of the domain, and become the username (e.g. `[email protected]` becomes `example`).
83
-
84
-
If your OpenID Connect provider requires client TLS certificates for authentication, you can configure them like so:
85
-
86
-
```console
87
-
CODER_TLS_CLIENT_CERT_FILE=/path/to/cert.pem
88
-
CODER_TLS_CLIENT_KEY_FILE=/path/to/key.pem
89
-
```
121
+
## OIDC Claims
90
122
91
123
Coder requires all OIDC email addresses to be verified by default. If the `email_verified` claim is present in the token response from the identity provider, Coder will validate that its value is `true`.
92
124
If needed, you can disable this behavior with the following setting:
> **Note:** This will cause Coder to implicitly treat all OIDC emails as "verified".
99
131
132
+
When a new user is created, the `preferred_username` claim becomes the username. If this claim is empty, the email address will be stripped of the domain, and become the username (e.g. `[email protected]` becomes `example`).
133
+
100
134
## SCIM (enterprise)
101
135
102
136
Coder supports user provisioning and deprovisioning via SCIM 2.0 with header
@@ -107,3 +141,12 @@ auth key and supply it the Coder server.
107
141
```console
108
142
CODER_SCIM_API_KEY="your-api-key"
109
143
```
144
+
145
+
## TLS
146
+
147
+
If your OpenID Connect provider requires client TLS certificates for authentication, you can configure them like so:
0 commit comments