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
fix(auth): stop offering account creation when registration is disabled
DISABLE_REGISTRATION blocks /signup server-side, but the invite flow, the
login form, the SSO form, and the CLI handoff all kept routing people there,
stranding invited users on a dead end. The flag also never covered OAuth
account creation, so social sign-in still minted accounts for unknown
identities.
|`DISABLE_REGISTRATION=true`| Blocks all new accounts — email/password, email OTP, and social sign-in. Only existing accounts can sign in, including to accept a workspace invitation. SSO is unaffected|
88
88
|`DISABLE_EMAIL_SIGNUP=true`| Blocks new email/password registrations; existing email login keeps working |
89
89
|`ALLOWED_LOGIN_DOMAINS`| Comma-separated domain allowlist, e.g. `acme.com,acme.co.uk`. Gates email sign-**in** as well as signup |
90
90
|`ALLOWED_LOGIN_EMAILS`| Comma-separated address allowlist, applied the same way |
@@ -93,7 +93,9 @@ See the [SSO guide](/platform/enterprise/sso) for identity-provider setup and th
93
93
|`BLOCKED_EMAIL_MX_HOSTS`| MX-host substrings to block; used only with the above |
94
94
95
95
<Callouttype="warn">
96
-
These controls gate the **email/password** path. A first-time sign-in through Google, GitHub, or Microsoft creates an account through the social provider and is not filtered by them. If you need a hard boundary, disable the social providers you have not vetted (`DISABLE_GOOGLE_AUTH`, `DISABLE_GITHUB_AUTH`, `DISABLE_MICROSOFT_AUTH`) or restrict membership at the identity provider and use SSO.
96
+
`ALLOWED_LOGIN_DOMAINS`, `ALLOWED_LOGIN_EMAILS`, and `SIGNUP_MX_VALIDATION_ENABLED` gate the **email/password** path only. A first-time sign-in through Google, GitHub, or Microsoft creates an account through the social provider and is not filtered by them. To restrict who may sign in through a social provider, disable the ones you have not vetted (`DISABLE_GOOGLE_AUTH`, `DISABLE_GITHUB_AUTH`, `DISABLE_MICROSOFT_AUTH`) or restrict membership at the identity provider and use SSO.
97
+
98
+
`DISABLE_REGISTRATION` and `BLOCKED_SIGNUP_DOMAINS` apply to every path, social included.
97
99
</Callout>
98
100
99
101
For a company deployment, the usual pairing is domain-restricted signup plus SSO:
Copy file name to clipboardExpand all lines: apps/docs/content/docs/en/platform/self-hosting/environment-variables.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ See [Authentication](/platform/self-hosting/authentication).
107
107
108
108
| Variable | Description |
109
109
|----------|-------------|
110
-
|`DISABLE_REGISTRATION`| Set `true` to disable new user signups entirely|
110
+
|`DISABLE_REGISTRATION`| Set `true` to block all new accounts, including social sign-in. Invitations still work for people who already have an account. SSO is unaffected|
111
111
|`DISABLE_EMAIL_SIGNUP`| Block new email/password registrations; existing email login keeps working |
112
112
|`ALLOWED_LOGIN_DOMAINS`| Restrict signups to domains (comma-separated) |
113
113
|`ALLOWED_LOGIN_EMAILS`| Restrict signups to specific emails (comma-separated) |
0 commit comments