[Feature] Add IDM/LDAP/OIDC/SAML/SCIM provisioning #2

Open
opened 2026-07-10 22:10:46 +02:00 by zemion · 3 comments
Owner

Moved from add-ideas/govoplan-core#131.

Reason: IDM/LDAP/OIDC/SAML/SCIM provisioning belongs to the IDM module.

Original issue body:

Imported from a backlog-like text file.

  • Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
  • Line: 336
  • Source kind: product
  • Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform

Imported item:

Add IDM/LDAP/OIDC/SAML/SCIM provisioning.
Moved from add-ideas/govoplan-core#131. Reason: IDM/LDAP/OIDC/SAML/SCIM provisioning belongs to the IDM module. Original issue body: <!-- codex-generic-backlog-fingerprint:df91afb9b1bcbcf6457a215c --> Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `336` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform` Imported item: ```text Add IDM/LDAP/OIDC/SAML/SCIM provisioning. ```
Author
Owner

Duplicate/related core issue add-ideas/govoplan-core#32 was closed into this canonical IDM provisioning issue: add-ideas/govoplan-core#32.

The core issue specifically called out LDAP/OIDC/SAML provisioning with OIDC likely first.

Duplicate/related core issue `add-ideas/govoplan-core#32` was closed into this canonical IDM provisioning issue: https://git.add-ideas.de/add-ideas/govoplan-core/issues/32. The core issue specifically called out LDAP/OIDC/SAML provisioning with OIDC likely first.
Author
Owner

Needs a bounded first protocol and an authority decision before implementation. Recommended order: SCIM 2.0 provisioning first; keep OIDC login/federation at the Identity/Access boundary; add read/scheduled LDAP or Active Directory synchronization second.

Decisions required:

  • authoritative source for create/update/disable/delete and whether GovOPlaN may write back;
  • immutable matching key, rename handling, collision/manual-review policy, group-to-function mapping, and deprovision grace period;
  • first concrete identity provider and supported protocol/profile.

Manual inputs required:

  • non-production metadata/endpoints, client credentials or service account, CA/signing material, test users/groups, and approved attribute mapping;
  • provider-side audit/export plus failure and credential-rotation test access.

After those inputs, the first slice can implement dry-run diff, explicit apply, replay-safe cursoring, quarantine/manual review, and governed provenance without blocking on all protocols.

Needs a bounded first protocol and an authority decision before implementation. Recommended order: SCIM 2.0 provisioning first; keep OIDC login/federation at the Identity/Access boundary; add read/scheduled LDAP or Active Directory synchronization second. Decisions required: - authoritative source for create/update/disable/delete and whether GovOPlaN may write back; - immutable matching key, rename handling, collision/manual-review policy, group-to-function mapping, and deprovision grace period; - first concrete identity provider and supported protocol/profile. Manual inputs required: - non-production metadata/endpoints, client credentials or service account, CA/signing material, test users/groups, and approved attribute mapping; - provider-side audit/export plus failure and credential-rotation test access. After those inputs, the first slice can implement dry-run diff, explicit apply, replay-safe cursoring, quarantine/manual review, and governed provenance without blocking on all protocols.
zemion added
status
needs-info
and removed
status
triage
labels 2026-08-21 14:20:46 +02:00
Author
Owner

Implementation update 2026-08-23: the approved first provisioning boundary is SCIM 2.0; OIDC remains authentication, not provisioning authority. Release v0.1.21 (commit 3dd7766) adds a provider-neutral RFC 7643/7644 Users/Groups client and deterministic dry-run plan with immutable matching, collision quarantine, revision checks, complete-snapshot deactivation safeguards, and no Access-role authority from SCIM groups. This broad issue remains open for governed plan application and target validation. A real target needs a named IdP, endpoint/auth method, stable immutable employee/person attribute, group scope, deprovision policy and test tenant.

Implementation update 2026-08-23: the approved first provisioning boundary is SCIM 2.0; OIDC remains authentication, not provisioning authority. Release v0.1.21 (commit 3dd7766) adds a provider-neutral RFC 7643/7644 Users/Groups client and deterministic dry-run plan with immutable matching, collision quarantine, revision checks, complete-snapshot deactivation safeguards, and no Access-role authority from SCIM groups. This broad issue remains open for governed plan application and target validation. A real target needs a named IdP, endpoint/auth method, stable immutable employee/person attribute, group scope, deprovision policy and test tenant.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-idm#2