Complete Binky portal acceptance
This commit is contained in:
parent
0d1c7e133a
commit
37fff67b9f
1 changed files with 6 additions and 1 deletions
|
|
@ -165,7 +165,7 @@ required API idempotency, provider-link persistence, and suspension calls.
|
|||
|
||||
```task
|
||||
id: USER-WP-0020-T07
|
||||
status: progress
|
||||
status: done
|
||||
priority: high
|
||||
state_hub_task_id: "b8d1c048-24d2-416c-908f-e500d63c6865"
|
||||
```
|
||||
|
|
@ -197,6 +197,11 @@ the provider permits, and make authenticator labels identify the account.
|
|||
privacyIDEA's future enrollment label is now `Coulomb: {user}@{realm}` at the
|
||||
otpauth issuer/account level; existing wallet entries require a local rename.
|
||||
|
||||
Live `/api/v1/me` acceptance confirmed the canonical KeyCape issuer,
|
||||
`tenant:friendly:binky`, Binky-only users/admins groups, roles `user` and
|
||||
`tenant-admin`, and AAL2 `pwd` + `otp` assurance with `mfa: true`. Attempts to
|
||||
open `tenant:platform` and `tenant:coulomb` administration were both denied.
|
||||
|
||||
## T08 - Closure and next-stage handoff
|
||||
|
||||
```task
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue