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/docs/configuration/auth/providers.mdx
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,11 @@ If there's an authentication provider you'd like us to support, please [reach ou
11
11
12
12
### Email / Password
13
13
---
14
-
Email / password authentication is enabled by default. It can be **disabled** by setting `AUTH_CREDENTIALS_LOGIN_ENABLED` to `false`.
14
+
Email / password authentication is enabled by default. You can toggle it from **Settings → Access** using the **Email login** setting.
15
+
16
+
The `AUTH_CREDENTIALS_LOGIN_ENABLED` environment variable is deprecated. It still works, but when it is set it overrides the UI setting and locks the toggle. Leave it unset to manage email login from the UI.
17
+
18
+
Email login can't be disabled when no other login method is configured (no SSO identity provider and no email-code login), since that would leave no way to sign in.
Copy file name to clipboardExpand all lines: docs/docs/configuration/environment-variables.mdx
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,6 @@ The following environment variables allow you to configure your Sourcebot deploy
10
10
11
11
| Variable | Default | Description |
12
12
| :------- | :------ | :---------- |
13
-
|`AUTH_CREDENTIALS_LOGIN_ENABLED`|`true`| <p>Enables/disables authentication with basic credentials. Username and passwords are stored encrypted at rest within the postgres database. Checkout the [auth docs](/docs/configuration/auth/authentication) for more info</p> |
14
13
|`AUTH_EMAIL_CODE_LOGIN_ENABLED`|`false`| <p>Enables/disables authentication with a login code that's sent to a users email. `SMTP_CONNECTION_URL` and `EMAIL_FROM_ADDRESS` must also be set. Checkout the [auth docs](/docs/configuration/auth/authentication) for more info </p> |
15
14
|`AUTH_SECRET`**(required)**| - | <p>Used to validate login session cookies. Genearte one with `openssl rand -base64 33`.</p> |
16
15
|`AUTH_SESSION_MAX_AGE_SECONDS`|`2592000` (30 days) | <p>Relative time from now in seconds when to expire the session.</p> |
@@ -24,7 +23,6 @@ The following environment variables allow you to configure your Sourcebot deploy
24
23
|`DATA_DIR`|`/data`| <p>The directory within the container to store all persistent data. Typically, this directory will be volume mapped such that data is persisted across container restarts (e.g., `docker run -v $(pwd):/data`)</p> |
25
24
|`DATABASE_URL`**(required)**| - | <p>Connection string of your Postgres database, e.g. `postgresql://user:password@host:5432/sourcebot`.</p><p>If you'd like to use a non-default schema, you can provide it as a parameter in the database url.</p><p>You can also use `DATABASE_HOST`, `DATABASE_USERNAME`, `DATABASE_PASSWORD`, `DATABASE_NAME`, and `DATABASE_ARGS` to construct the database url.</p> |
26
25
|`EMAIL_FROM_ADDRESS`|`-`| <p>The email address that transactional emails will be sent from. See [this doc](/docs/configuration/transactional-emails) for more info.</p> |
27
-
| `FORCE_ENABLE_ANONYMOUS_ACCESS` | `false` | <p>When enabled, [anonymous access](/docs/configuration/auth/access-settings#anonymous-access) to the organization will always be enabled</p>
28
26
| `REQUIRE_APPROVAL_NEW_MEMBERS` | - | <p>When set, controls whether new users require approval before accessing your deployment. If not set, the setting can be configured via the UI. See [member approval](/docs/configuration/auth/access-settings#member-approval) for more info.</p>
29
27
|`REDIS_URL`**(required)**| - | <p>Connection string of your Redis instance, e.g. `redis://host:6379`.</p><p>To enable TLS, see [this doc](/docs/deployment/infrastructure/redis#tls).</p> |
30
28
|`REDIS_REMOVE_ON_COMPLETE`|`0`| <p>Controls how many completed jobs are allowed to remain in Redis queues</p> |
@@ -54,10 +52,8 @@ The following environment variables allow you to configure your Sourcebot deploy
54
52
|`AUTH_EE_GCP_IAP_AUDIENCE`| - | <p>The GCP IAP audience to use when verifying JWT tokens. Must be set to enable GCP IAP JIT provisioning</p> |
|`PERMISSION_SYNC_REPO_DRIVEN_ENABLED`|`true`| <p>Enables/disables [repo-driven permission syncing](/docs/features/permission-syncing#how-it-works). Only applies when `PERMISSION_SYNC_ENABLED` is `true`.</p> |
57
-
|`EXPERIMENT_EE_PERMISSION_SYNC_ENABLED`**(deprecated)**|`false`| <p>Deprecated. Use `PERMISSION_SYNC_ENABLED` instead.</p> |
58
55
|`AUTH_EE_ALLOW_EMAIL_ACCOUNT_LINKING`|`true`| <p>When enabled, different SSO accounts with the same email address will automatically be linked.</p> |
59
56
|`DISABLE_API_KEY_CREATION_FOR_NON_OWNER_USERS`|`false`| <p>When enabled, only organization owners can create API keys. Non-owner members will receive a `403` error if they attempt to create one.</p> |
60
-
|`EXPERIMENT_DISABLE_API_KEY_CREATION_FOR_NON_ADMIN_USERS`**(deprecated)**|`false`| <p>Deprecated. Use `DISABLE_API_KEY_CREATION_FOR_NON_OWNER_USERS` instead.</p> |
61
57
|`DISABLE_API_KEY_USAGE_FOR_NON_OWNER_USERS`|`false`| <p>When enabled, only organization owners can create or use API keys. Non-owner members will receive a `403` error if they attempt to create or authenticate with an API key. If you only want to restrict creation (not usage), use `DISABLE_API_KEY_CREATION_FOR_NON_OWNER_USERS` instead.</p> |
0 commit comments