From b1e51ab0fba537129a7d69dab88b82b0601e5553 Mon Sep 17 00:00:00 2001 From: stratself Date: Wed, 16 Sep 2026 17:14:16 +0000 Subject: [PATCH] docs(internal auth): Redo rego methods (see commit notes) * Tokens + recaptcha combinations have been removed since they don't work. Docstring in config tomlto be removed later * Method 3 expanded to include both static and admin issued tokens * Methods 1-3 are the "trusted token flow" and 4-6 are the "untrusted captcha flow" --- docs/authentication/internal.mdx | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/docs/authentication/internal.mdx b/docs/authentication/internal.mdx index e1d8bb763..05542b573 100644 --- a/docs/authentication/internal.mdx +++ b/docs/authentication/internal.mdx @@ -6,16 +6,14 @@ Continuwuity comes with an internal database for user authentication, which it u Registration is disabled by default. To enable it, set `allow_registration = true` in your config file and use at least one of the registration methods below. -| Method | Description | Additional configuration needed | -| ------ | --------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | -| 1 | Admin-issued tokens (recommended) | None. Use the [`!admin token issue`](../reference/admin/token#admin-token-issue) command | -| 2 | Static registration token | `registration_token` or `registration_token_file` | -| 3 | reCAPTCHA-only registration | `recaptcha_site_key` and `recaptcha_private_site_key` | -| 4 | Email-only registration | `require_email_for_registration = true` in `[global.smtp]` section. See [Email configuration](#email-configuration) | -| 5 | Static token + reCAPTCHA | Methods 2 + 3 | -| 6 | Email + reCAPTCHA | Methods 3 + 4 | -| 7 | Static token + email | Method 2 + `require_email_for_token_registration = true` in `[global.smtp]`. See [Email configuration](#email-configuration) | -| 8 | Static token + email + reCAPTCHA | Methods 3 + 7 | +| Method | Description | Additional configuration needed | +| ------ | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- | +| 1 | Admin-issued tokens (recommended) | None. Use the [`!admin token issue`](../reference/admin/token#admin-token-issue) command | +| 2 | Static registration token | `registration_token` or `registration_token_file` | +| 3 | Token + email | Method 1 or 2 + `require_email_for_token_registration = true` in `[global.smtp]`. See [Email configuration](#email-configuration) | +| 4 | Email-only registration | `require_email_for_registration = true` in `[global.smtp]` section. See [Email configuration](#email-configuration) | +| 5 | reCAPTCHA-only registration | `recaptcha_site_key` and `recaptcha_private_site_key` | +| 6 | Email + reCAPTCHA registration | Methods 4 + 5 | Admin-issued tokens are the recommended registration method. These tokens are well suited for private or invite-only servers, and they can be scoped with an expiry duration or given a usage limit. See the [`!admin token`](../reference/admin/token) commands for more details.