DekEn

อัปเดต 2026-09-07

Per-org OIDC SSO & JIT enrollment

OpenID Connect, domain-routed, group→role mapping

Per-organization single sign-on via OpenID Connect (OIDC): employees are routed to their own identity provider by verified email domain and just-in-time (JIT) enrolled into the org on first login, with identity-provider groups optionally mapped straight to a DekEn role.

เมื่อไรจึงใช้
  • An enterprise customer wants staff to log in with their existing corporate identity provider, not a DekEn password
  • You're standing up SSO for a new org and need the setup order (domain verification comes first)
  • You want IdP group membership to drive DekEn role assignment automatically instead of manual per-user role edits
คำนวณอย่างไร

OIDC routes a login by the user's email domain to the org's configured identity provider; a first-time login auto-enrolls (JIT) the user into that org rather than requiring manual pre-creation; an optional group→role mapping translates IdP groups into DekEn roles, capped so SSO alone can never grant more than a site-manager-level role. Domain ownership is proven with a DNS TXT record before routing activates.

ข้อควรระวัง
noteSSO routing only activates after the organization proves domain ownership via DNS — routing logins by an unverified email domain was an identified account-takeover risk and is deliberately blocked until verification passes.
noteGroup→role mapping is capped — it cannot be used to silently mint a platform admin via IdP group membership.
ที่เกี่ยวข้อง