The served schema's Account section gets a Passkeys link under Credentials, after Password, pointing at the console's own page CustomComponent/Passkeys. Regular users could only reach the Passkeys card on Directory › Accounts, which they can't open.
Only resources/schema/schema.json.gz + .sha256 change (encoded like tools/fork/expr-schema.py; the rest round-trips byte for byte).
No permission change: the default user role already holds the sysPasskey* permissions. Saved permission lists are #478.
Checked: fork checks, expr-schema.py --check; local preview as a non-admin account: the Credentials menu reads Password · Passkeys · App Passwords · API Keys, and the page lists, adds and removes the user's own passkeys.
For inbuxa/inbuxa-admin#250 (forum t/338, t/339).
The served schema's Account section gets a **Passkeys** link under Credentials, after Password, pointing at the console's own page `CustomComponent/Passkeys`. Regular users could only reach the Passkeys card on Directory › Accounts, which they can't open.
- Only `resources/schema/schema.json.gz` + `.sha256` change (encoded like `tools/fork/expr-schema.py`; the rest round-trips byte for byte).
- No permission change: the default user role already holds the `sysPasskey*` permissions. Saved permission lists are #478.
- A console without the page hides the link.
Pairs with inbuxa/inbuxa-admin#251.
**Checked:** fork checks, `expr-schema.py --check`; local preview as a non-admin account: the Credentials menu reads Password · Passkeys · App Passwords · API Keys, and the page lists, adds and removes the user's own passkeys.
The served schema's Account section gets a Passkeys link under
Credentials, after Password, pointing at the console's own page
(CustomComponent/Passkeys). It lets anyone who can sign in to the console
manage their own passkeys; until now the card was only on Directory ›
Accounts, which regular users can't open.
The default user role already holds the sysPasskey* permissions, so no
permission change. A console without the page hides the link.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For inbuxa/inbuxa-admin#250 (forum t/338, t/339).
The served schema's Account section gets a Passkeys link under Credentials, after Password, pointing at the console's own page
CustomComponent/Passkeys. Regular users could only reach the Passkeys card on Directory › Accounts, which they can't open.resources/schema/schema.json.gz+.sha256change (encoded liketools/fork/expr-schema.py; the rest round-trips byte for byte).sysPasskey*permissions. Saved permission lists are #478.Pairs with inbuxa/inbuxa-admin#251.
Checked: fork checks,
expr-schema.py --check; local preview as a non-admin account: the Credentials menu reads Password · Passkeys · App Passwords · API Keys, and the page lists, adds and removes the user's own passkeys.