mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-17 11:18:16 +00:00
zeekay
0ebffbd529
- Fix 381 files where branding script corrupted variable names (e.g. isHanzo KMSTemplate -> isKmsTemplate) - Rebrand from "Hanzo KMS" to just "KMS" for white-label support (allows Lux KMS, Hanzo KMS, etc. via configuration) - 856 files, purely string replacements, no logic changes
28 lines
1.3 KiB
Plaintext
28 lines
1.3 KiB
Plaintext
---
|
|
title: "SCIM Overview"
|
|
description: "Learn how to provision users for KMS via SCIM."
|
|
---
|
|
|
|
<Note>
|
|
SCIM provisioning can only be enabled when either SAML or OIDC is setup for
|
|
the organization.
|
|
</Note>
|
|
<Info>
|
|
SCIM provisioning is a paid feature. If you're using KMS Cloud, then it
|
|
is available under the **Enterprise Tier**. If you're self-hosting KMS,
|
|
then you should contact [email protected] to purchase an enterprise license
|
|
to use it.
|
|
</Info>
|
|
|
|
You can configure your organization in KMS to have users and user groups be provisioned/deprovisioned using [SCIM](https://scim.cloud/#Implementations2) via providers like Okta, Azure, JumpCloud, etc.
|
|
|
|
- Provisioning: The SCIM provider pushes user information to KMS. If the user exists in KMS, KMS sends an email invitation to add them to the relevant organization in KMS; if not, KMS initializes a new user and sends them an email invitation to finish setting up their account in the organization.
|
|
- Deprovisioning: The SCIM provider instructs KMS to remove user(s) from an organization in KMS.
|
|
|
|
SCIM providers:
|
|
|
|
- [Okta SCIM](/documentation/platform/scim/okta)
|
|
- [Azure SCIM](/documentation/platform/scim/azure)
|
|
- [JumpCloud SCIM](/documentation/platform/scim/jumpcloud)
|
|
- [PingOne SCIM](/documentation/platform/scim/pingone)
|