mirror of
https://github.com/awatertrevi/infisical.git
synced 2026-09-22 13:39:35 +00:00
Complete preliminary SCIM fns, add permissioning to SCIM, add docs for SCIM
This commit is contained in:
74
docs/documentation/platform/scim/azure.mdx
Normal file
74
docs/documentation/platform/scim/azure.mdx
Normal file
@@ -0,0 +1,74 @@
|
||||
---
|
||||
title: "Azure SCIM"
|
||||
description: "Configure SCIM provisioning with Azure for Infisical"
|
||||
---
|
||||
|
||||
<Info>
|
||||
Azure SCIM provisioning is a paid feature.
|
||||
|
||||
If you're using Infisical Cloud, then it is available under the **Enterprise Tier**. If you're self-hosting Infisical,
|
||||
then you should contact team@infisical.com to purchase an enterprise license to use it.
|
||||
</Info>
|
||||
|
||||
Prerequisites:
|
||||
- [Configure Azure SAML for Infisical](/documentation/platform/sso/azure)
|
||||
|
||||
<Steps>
|
||||
<Step title="Create a SCIM token in Infisical">
|
||||
In Infisical, head to your Organization Settings > Authentication > SCIM Configuration and
|
||||
press the **Enable SCIM provisioning** toggle to allow Azure to provision/deprovision users for your organization.
|
||||
|
||||

|
||||
|
||||
Next, press **Manage SCIM Tokens** and then **Create** to generate a SCIM token for Azure.
|
||||
|
||||

|
||||
|
||||
Next, copy the **SCIM URL** and **New SCIM Token** to use when configuring SCIM in Azure.
|
||||
|
||||

|
||||
</Step>
|
||||
<Step title="Configure SCIM in Azure">
|
||||
In Azure, head to your Enterprise Application > Provisioning > Overview and press **Get started**.
|
||||
|
||||

|
||||
|
||||
Next, set the following fields:
|
||||
|
||||
- Provisioning Mode: Select **Automatic**.
|
||||
- Tenant URL: Input **SCIM URL** from Step 1.
|
||||
- Secret Token: Input the **New SCIM Token** from Step 1.
|
||||
|
||||
Afterwards, press the **Test Connection** button to check that SCIM is configured properly.
|
||||
|
||||

|
||||
|
||||
After you hit **Save**, select **Provision Microsoft Entra ID Users** under the **Mappings** subsection.
|
||||
|
||||

|
||||
|
||||
Next, adjust the mappings so you have them configured as below:
|
||||
|
||||

|
||||
|
||||
Finally, head to your Enterprise Application > Provisioning and set the **Provisioning Status** to **On**.
|
||||
|
||||

|
||||
|
||||
Alternatively, you can go to **Overview** and press **Start provisioning** to have Azure start provisioning/deprovisioning users to Infisical.
|
||||
|
||||

|
||||
|
||||
Now Azure can provision/deprovision users to/from your organization in Infisical.
|
||||
</Step>
|
||||
</Steps>
|
||||
|
||||
**FAQ**
|
||||
|
||||
<AccordionGroup>
|
||||
<Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
|
||||
Infisical's SCIM implmentation accounts for retaining the end-to-end encrypted architecture of Infisical because we decouple the **authentication** and **decryption** steps in the platform.
|
||||
|
||||
For this reason, SCIM-provisioned users are initialized but must finish setting up their account when logging in the first time by creating a master encryption/decryption key. With this implementation, IdPs and SCIM providers cannot and will not have access to the decryption key needed to decrypt your secrets.
|
||||
</Accordion>
|
||||
</AccordionGroup>
|
||||
Reference in New Issue
Block a user