Skip to content

SCIM provisioning #34

Closed
Closed

Description

@Adron

No SCIM endpoints exist. Larger customers can't have their own IdP push User lifecycle events (create, update, deactivate, and group or org membership) into the hub.

Spec: Roadmap → Phase 3, plan-remaining.md → Phase 3.

Trigger: a customer large enough to require it. It will most likely arrive alongside the SSO broker work.

Scope:

  • SCIM 2.0 /Users and /Groups (mapped to Organization memberships), scoped to one Organization
  • A SCIM bearer credential per Organization (probably an Organization-scoped API Key)
  • Map deactivation onto the existing suspend and revoke path, so access.revoked fires
  • Audit events, OpenAPI, tests, and the Changelog

Activity

  1. Adron commented on Oct 22, 2026

    @Adron
    MemberAuthor

    Built in the SCIM PR linked from this issue (SCIM 2.0 Users, token management; provisioning invites, deprovisioning removes the membership).

  2. Adron commented on Oct 22, 2026

    @Adron
    MemberAuthor

    Built in #62.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions