From 8a6ed7cc711e797542a531091b3bdbc73e5f61e4 Mon Sep 17 00:00:00 2001 From: tv Date: Mon, 9 Nov 2026 02:24:51 +0000 Subject: dashboard: keys edited, the last removed with a password, failures kept The credentials dialog listed a user's keys whole, to add one or remove one but the last, and any failure replaced the dialog with the error, the form lost. * A key is shown short: its type, the first and last four characters of what tells it apart (an Ed25519 key's base64 after the part all of them share), its comment; the whole line in its tooltip. * A key can be edited, its name and its line: saved under the name, a new name written first and the old one removed. * A user with a password on this node (`--htpasswd`) may remove its last key: it logs in by the password. GET /auth/keys says so (`password`), and DELETE /auth/keys/{id} takes it then; the rules no longer keep the last key on every node (no other node can tell who has a password where; under a strict policy the signed entry keeps one still). * What fails says why beside where it was asked (the add form, the edited row, the removed one), which stays as it was, to be set right and tried again. --- src/api/auth.rs | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'src/api/auth.rs') diff --git a/src/api/auth.rs b/src/api/auth.rs index a5a987c..ac70b82 100644 --- a/src/api/auth.rs +++ b/src/api/auth.rs @@ -154,6 +154,13 @@ impl Range { } impl AuthState { + /// Whether `user` has a password on this node (`--htpasswd`): it logs in by it. + pub(crate) fn has_password(&self, user: &str) -> bool { + self.users + .as_ref() + .is_some_and(|users| users.contains_key(user)) + } + /// From the options; None if there is neither an htpasswd file nor a user header /// (no users: no HTTP API, for a relay). pub(crate) fn from_settings( -- cgit v1.3.1