spec: single sign-on (12), OpenID Connect and LDAP
Owner decisions 2026-10-25: a user connects their OpenID account and signs in with either it or their password; the admin picks passwords only, OpenID only (admins keep a password way in), or mixed. No automatic accounts. OIDC sessions re-checked every 15 min with the refresh token; signing out also signs out at the provider; password sign-ins keep two-step. LDAP is one more way to check a password. Decision 0004: openid-client and ldapts. Tasks S1-S5.
This commit is contained in:
1 parent
95561f651f
commit
ba293f8703
5 files changed
+484
-1
No files matched your search
@@ -9,7 +9,9 @@ Legend: 📖 read · 🔨 build · ✅ done when
|
||||
---
|
||||
|
||||
## Backlog (owner's order, 2026-10-21)
|
||||
0. **Contacts** (owner, 2026-10-23: needed next), tasks C1–C6 in [11 §6](11-contacts.md#6-order-of-work):
|
||||
0. **Single sign-on** (owner, 2026-10-25: next), tasks S1–S5 in [12 §8](12-sso.md#8-order-of-work):
|
||||
OpenID Connect (any provider; the owner uses Keycloak), then LDAP/LDAPS.
|
||||
0. Done: **Contacts** (owner, 2026-10-23), tasks C1–C6 in [11 §6](11-contacts.md#6-order-of-work):
|
||||
Simple (builtin phonebook) or Robust (Contrack), picked in the setup wizard. The owner uses
|
||||
Contrack.
|
||||
1. **Grandstream HT802 V2 set up automatically** (step 3 of
|
||||
|
||||
Reference in new issue
Block a user