Part of #334. Found in the passkey click-through: with passkeys off for an account, the webmail and console offered "Add a passkey" and only learned from the refusal.
urn:inbuxa:jmap on the signed-in account gets passkeysAllowed and maxPasskeys. passkeysAllowed is true when the principal holds sysPasskeyCreate and allowed_for (PK-12, PK-13) leaves passkeys on for it.
New PK-19 and acceptance test 12 in docs/spec/features/passkeys.md.
Clients already read it and fall back when it's missing: webmail #117 and console #248 (merged).
No schema change: the session isn't in the registry schema.
Checked locally: cargo check -p jmap -p tests --all-targets, cargo fmt --check, every fork check and its unit tests, system::passkeys::passkey_tests (new assertions: true with the limit, false once the domain switches passkeys off) and jmap::jmap_tests (the session expectation in principal/get).
Part of #334. Found in the passkey click-through: with passkeys off for an account, the webmail and console offered "Add a passkey" and only learned from the refusal.
- `urn:inbuxa:jmap` on the signed-in account gets `passkeysAllowed` and `maxPasskeys`. `passkeysAllowed` is true when the principal holds `sysPasskeyCreate` and `allowed_for` (PK-12, PK-13) leaves passkeys on for it.
- New PK-19 and acceptance test 12 in `docs/spec/features/passkeys.md`.
- Clients already read it and fall back when it's missing: webmail #117 and console #248 (merged).
- No schema change: the session isn't in the registry schema.
Checked locally: `cargo check -p jmap -p tests --all-targets`, `cargo fmt --check`, every fork check and its unit tests, `system::passkeys::passkey_tests` (new assertions: true with the limit, false once the domain switches passkeys off) and `jmap::jmap_tests` (the session expectation in principal/get).
The urn:inbuxa:jmap capability on the signed-in account now carries
passkeysAllowed (holds sysPasskeyCreate and no server, tenant or domain
switch or external directory turns passkeys off for it) and maxPasskeys.
Clients use it to say up front that passkeys are off or the account is at
its limit, instead of offering an add the server will refuse. Older
servers leave both out and clients fall back to the refusal.
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.
Part of #334. Found in the passkey click-through: with passkeys off for an account, the webmail and console offered "Add a passkey" and only learned from the refusal.
urn:inbuxa:jmapon the signed-in account getspasskeysAllowedandmaxPasskeys.passkeysAllowedis true when the principal holdssysPasskeyCreateandallowed_for(PK-12, PK-13) leaves passkeys on for it.docs/spec/features/passkeys.md.Checked locally:
cargo check -p jmap -p tests --all-targets,cargo fmt --check, every fork check and its unit tests,system::passkeys::passkey_tests(new assertions: true with the limit, false once the domain switches passkeys off) andjmap::jmap_tests(the session expectation in principal/get).