From 4631854325aab6845d4244ebb7e3af3089781a9d Mon Sep 17 00:00:00 2001 From: stratself Date: Sat, 12 Sep 2026 16:04:32 +0000 Subject: [PATCH] docs(auth): Address concerns from feedback part 1 --- docs/authentication.mdx | 6 +++--- docs/authentication/internal.mdx | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/authentication.mdx b/docs/authentication.mdx index cd30b8df7..3f2edb895 100644 --- a/docs/authentication.mdx +++ b/docs/authentication.mdx @@ -6,14 +6,14 @@ This chapter describes various ways to authenticate to Continuwuity. Continuwuity implements the following authentication flows: -- **OAuth login** (also known as **next-gen auth**): clients redirect the user to Continuwuity's login/signup page. -- **Legacy login** (also known as the **UIAA** framework): clients logs in/signs up directly to the server via its own UI. +- **OAuth login** (also known as **next-gen auth**): clients redirect the user to Continuwuity's own login and registration page to complete the authentication process. +- **Legacy login** (also known as the **UIAA** framework): clients provide their own UI to log in to or register with the server directly. Different sets of clients support different flows, but most clients are moving towards next-gen auth. One can set which login mode(s) are allowed via the `compatibility_mode` variable of the `[global.oauth]` config file section. :::important Configure your client well-known for OAuth logins -To ensure OAuth logins work, Continuwuity must know the path from which its Client-Server API is being served from: +To ensure OAuth logins work, Continuwuity must know the base URL its Client-Server API is being served on: ```toml [global.well_known] diff --git a/docs/authentication/internal.mdx b/docs/authentication/internal.mdx index ab186cc13..727ea5cfb 100644 --- a/docs/authentication/internal.mdx +++ b/docs/authentication/internal.mdx @@ -1,6 +1,6 @@ # Internal authentication -Continuwuity by default comes with an internal database for user authentication. Using the internal database allows for self-servicing of account registration, linking emails, and password resets. +Continuwuity comes with an internal database for user authentication, which it uses by default. This allows for self-servicing of account registration, linking emails, and password resets. ## Registration @@ -16,7 +16,7 @@ Registration is disabled by default. To enable it, set `allow_registration = tru | 6 | Static token + email + reCAPTCHA | Methods 3 + 5 | | 7 | Email only | `require_email_for_registration = true` in `[global.smtp]` section. See [Email configuration](#email-configuration) | -Registrations can be made via Continuwuity's account management page, as well as in-band from within a Matrix client (if legacy login is enabled). +Users can register on Continuwiity's account management page, or directly within a Matrix client if legacy login is enabled. Admin-issued tokens are the recommended method of registration. These tokens can be scoped with an expiry duration or maximum times used, and are suited for private/invite-only homeservers. See the `!admin token` commands for more details.