List, switch off/on and delete Authentik users
Apps → Authentik gets a Users section for administrators: a searchable list of people (service accounts left out) with status, administrator and last sign-in, and Switch off / Switch on / Delete. Switching off sends only is_active; deleting needs the user name typed and re-checked by the server. The server refuses service accounts, the account the token belongs to and the last active administrator. Each action is audited. The token field is now "Token for making and managing users". Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
aa95d6b314
commit
0cd11268ee
12 files changed
+733
-21
No files matched your search
+7
-3
@@ -518,14 +518,18 @@ osTicket's API cannot close a ticket, so this is the one place in the app that *
|
||||
|
||||
### Authentik
|
||||
|
||||
- **Config fields:** the **address** of Authentik (`https://auth.example.lan`), an **API token** (Authentik → Directory → Tokens and App passwords → *Create*, intent **API Token**, for a user who may read; stored encrypted), optionally a **token for making users** (below) and, for an https address with a certificate you made yourself, *insecure*.
|
||||
- **Config fields:** the **address** of Authentik (`https://auth.example.lan`), an **API token** (Authentik → Directory → Tokens and App passwords → *Create*, intent **API Token**, for a user who may read; stored encrypted), optionally a **token for making and managing users** (below) and, for an https address with a certificate you made yourself, *insecure*.
|
||||
- **Required access:** read only. This app only ever sends GET requests: the version, the workers, the outposts and their health, the certificates, the tokens and the events log. **Nothing is ever changed.** Give the token a user with just enough to read these (an administrator, or a user in a role that may view them);
|
||||
if one of the lists is refused, that part is left out and the rest still works.
|
||||
- **Making a user (optional, administrators only):** with a second, separate token in *Token for making users* — an API token of an account that may add users, which is close to an administrator of Authentik, so give it only if you want this — **Apps → Authentik → New user** makes a user
|
||||
- **Making and managing users (optional, administrators only):** with a second, separate token in *Token for making and managing users* — an API token of an account that may add, change and delete users, which is close to an administrator of Authentik, so give it only if you want this — **Apps → Authentik → New user** makes a user
|
||||
(user name, name, an email if there is one, and groups, which are read from Authentik when the form opens; a group that makes members administrators of Authentik is marked) and then a **one-time recovery link** for them. They open the link and **choose their own password**: this app never sets, sees or keeps one.
|
||||
The link is in the answer to that one request and nowhere else (not stored, not in the audit log); the audit log has *who made which user* and *who made a link for whom*, never the link or a token. If the user is made and the link is not (Authentik needs a **recovery flow** on the brand — System → Brands),
|
||||
the page says so and the link is made in Authentik (the user → *Create recovery link*). Authentik builds the link from the address it was called at, so the integration's address should be the one people use. The token for making users is only used for this; reading Authentik never uses it,
|
||||
and *Stop allowing this* on the page removes it again (the reading token stays). Without it nothing about the page changes for anyone but an administrator, who sees where to add one. The calls (`GET /core/groups/`, `POST /core/users/`, `POST /core/users/{id}/recovery/`, asking for a link that lasts a day, which a version of
|
||||
and *Stop allowing this* on the page removes it again (the reading token stays).
|
||||
**Users** on the same page lists the people (service accounts — what an outpost or an integration signs in with — are left out), searchable, with whether each is on, whether they are an administrator and when they last signed in, and lets an administrator **switch a user off** (a `PATCH` of `is_active` and nothing else;
|
||||
they can no longer sign in, nothing of theirs is lost, *Switch on* brings it back) or **delete** one (a `DELETE`, for good: the user name has to be typed, and is checked again by the server against the user as Authentik has them now). **Refused, by the server, with the reason:** a service account, the account the token
|
||||
itself belongs to, and the last active administrator (so nobody can be locked out, or the sign-in in front of everything else cut off); do those in Authentik. Each is in the audit log (*who switched off / on / deleted which user*). Switching off or deleting someone in Authentik does not end a session they
|
||||
already have in this app: end it under Users → *Signed in now*. Lists are read 200 at a time. Without it nothing about the page changes for anyone but an administrator, who sees where to add one. The calls (`GET /core/groups/`, `POST /core/users/`, `POST /core/users/{id}/recovery/`, `GET /core/users/`, `GET /core/users/{id}/`, `GET /core/users/me/`, `PATCH` and `DELETE /core/users/{id}/`; asking for a link that lasts a day, which a version of
|
||||
Authentik that does not take that sets for itself) are **not verified against a live Authentik**; the tests use a pretend one.
|
||||
- **What it does:** every **five minutes** Authentik is read and stored — its version (and whether a newer one is out), whether a **worker** is connected, each **outpost** (the proxy outpost that guards your apps, an LDAP one) with how many instances reported in during the last five minutes and whether they run the right version, the
|
||||
**certificates** (those Authentik does not renew by itself) with their expiry, the **API tokens and app passwords** that expire, and how many **sign-ins failed** and **configuration errors** happened in the last day. **Apps → Authentik** shows it, with what runs out soonest first.
|
||||
|
||||
Reference in new issue
Block a user