There are additional configuration options available for the SAML 2.0 protocol than are referenced in this guide, which only outlines the required settings. For details about the additional options, see the SAML protocol configuration options reference guide.

1. Navigate to the Immuta App Settings page.

2. Scroll to the Identity Management section and click Add IAM.

3. Complete the Display Name field and select SAML from the Identity Provider Type dropdown.

4. Take note of the ID and copy the SSO Callback URL to use as the ACS URL in your identity provider.

5. Adjust Default Permissions granted to users by selecting from the list in this dropdown menu.

6. Complete the Entry Point field. This is the location of your single sign on application that will be redirected to from the Immuta login page.

7. Upload your Signing Certificate. This is your identity provider's public signing certificate.

8. Opt to Enable SCIM support for SAML. Validate that the usernames in your IAM match those in your data platform (Snowflake, Databricks, etc.). If they are incorrect in the IAM or the casing doesn't match, fix the data platform username in the identity provider before configuring SCIM in Immuta.

9. In the Profile Schema section, map attributes in SAML to automatically fill in a user's Immuta profile. Note: Fields that you specify in this schema will not be editable by users within Immuta.

10. Click Test Connection and Test User Login.

11. Save your configuration.

Immuta can integrate with Microsoft Entra ID as an IAM over SAML 2.0. This page outlines how to register Immuta as an Azure Enterprise Application with Single Sign-On over SAML 2.0.

Create an Enterprise Application

1. In the Microsoft Azure portal, browse to Enterprise Applications.

2. Click the New Application button and then select Create your own application.

3. Name the application with the name of your choice, select Integrate any other application you don't find in the gallery (Non-gallery), and click Create.

4. On the left menu, choose the Single sign-on menu item and then pick the SAML tile.

5. In the first section (Basic SAML Configuration), click the Edit icon and fill in Identifier (Entity ID) field with the full URI of your Immuta app (e.g., https://immuta.my-comany.com).

6. In the second section (User Attributes & Claims), specify the unique user identifier you want to use in Immuta. Common choices are the mail claim or the userprincipalname claim. You can also specify the user claims you want Azure to expose to Immuta. You will use the names of those claims to map them to Immuta user attributes when you create an IAM.

7. In the third section (SAML Signing Certificate), click the Download link next to Certificate (Base64) and save the file on your hard drive:

8. In the fourth section, copy the Login URL and save it for when you will create the IAM through the Immuta UI.

Now that you have an enterprise application in place, continue to create and configure an IAM in Immuta. You will need a few details from the Immuta UI to complete the configuration of the enterprise application.

Attribute matching for SCIM

Attribute matching allows you to determine how to uniquely identify a user in Microsoft Entra ID and match that user in Immuta at login and during provisioning. Immuta supports the following matching attributes in Microsoft Entra ID:

• Users:

  • id

  • userName

  • email

  • displayName

  • emails[type eq "work"].value

• Groups

  • id

  • displayName (See the limitation below for group names.)

Using any other attribute in Microsoft Entra ID as a matching attribute results in an error. See the Microsoft Entra ID documentation for details about attribute matching and how to configure it.

Create an IAM

1. In Immuta, browse to App Settings, go to the Identity Managers section, and click Add IAM

2. Assign a name to the new IAM. Immuta will automatically derive the ID of the IAM from the name you pick.

3. Select SAML in the Identity Provider Type drop-down.

4. Start configuring the new IAM:

   • Default Permissions: The default permission that should be assigned to a Microsoft Entra ID user in Immuta.

   • Issuer: This field needs to have the same value as the Identifier (Entity ID) of the enterprise application (e.g., https://immuta.my-comany.com).

   • Entry Point: Paste the Login URL that you obtained in the previous section.

   • User ID Attribute: This field is the attribute that will contain the username of the user logging in.

   • Signing Certificate: Upload the certificate file you have previously downloaded and converted into a PEM encoded certificate.

   • Decryption Private Key: This field is the optional key for decrypting attribute assertions.

   • Enable SCIM support for SAML: Opt to enable SCIM support. Validate that the usernames in your IAM match those in your data platform (Snowflake, Databricks, etc.). If they are incorrect in the IAM or the casing doesn't match, fix the data platform username in the identity provider before configuring SCIM in Immuta.

   • Profile Schema: Map attributes in SAML to automatically fill in a user's Immuta profile. Note: Fields that you specify in this schema will not be editable by users within Immuta.

   • Enable any optional settings:

     • Link SQL

     • Allow Identity Provider Initiated Single Sign On: After checking this option, set disableRequestedAuthnContext to true under Additional Config Parameters.

     • Sync groups from SAML to Immuta

     • Sync attributes from SAML to Immuta: After selecting this checkbox, map your Entra ID attributes to Immuta in the Attribute Schema section.

     • External Groups and Attributes Endpoint

   Before you can test the integration and save the new IAM, you will need to go back to the Microsoft Azure Portal and fill in the Reply URL.

5. In the Single sign-on page of your enterprise application, edit the first section with the title Basic SAML Configuration.

6. Fill in the Reply URL (Assertion Consumer Service URL) field with a value that adheres to the following format: ${IMMUTA_URL}/bim/iam/${IAM_ID}/user/authenticate/callback. For example, if the URL to your Immuta tenant is https://immuta.my-comany.com and the assigned IAM ID is MicrosoftEntraID, the value of the Reply URL field should be https://immuta.my-comany.com/bim/iam/MicrosoftEntraID/user/authenticate/callback. To save the changes, click Save. You can find the IAM ID that Immuta has assigned to the IAM in the form.

7. You should now be able to test the IAM and save it. After clicking Test Connection and letting Immuta hit the enterprise application URL, you will need to verify that the authentication flow works before you can save and create the IAM. To do so, click Test User Login and follow the instructions.

8. Save the changes in Immuta.

Microsoft Entra ID SCIM limitation

SCIM will skip updates and will not inform Immuta that an attribute should be removed from a user in the following scenarios, even if the attribute mapping has been deleted from the IAM configuration on the Immuta app settings page:

• Attribute is set to empty (removed) in Microsoft Entra ID

• Attribute is deleted in Microsoft Entra ID

In both of these scenarios, Azure doesn’t send Immuta a payload to remove the attribute, as it considers the action a redundant export. As a result, the attribute values that previously existed in Microsoft Entra ID will not get removed from the user in Immuta.

To remediate this limitation, take one of the following actions:

• Change the attribute to a non-impacting value other than empty in Microsoft Entra ID.

• Alternatively, remove the attribute mapping from the attribute schema section of the IAM configuration on the Immuta app settings page. Then, trigger an update for that user in Microsoft Entra ID by making a change to any value for that user. Microsoft Entra ID will send an update for that user to Immuta, and Immuta will remove the attribute from the user. Note that if that attribute mapping is ever re-added in Immuta on the app settings page, that attribute will be added to the user again.

See Known issues for provisioning in Microsoft Entra ID for more details about this limitation.

Limitation

Group names containing " are unsupported in the Microsoft Entra ID integration.

This section includes a general guide for configuring a SAML provider and guides for specific SAML providers in Immuta. The getting started section below provides best practices for setup and configuration.

Getting started with SAML

1. Start by creating a few initial and so that you know the user metadata you will need from your IAM. For example, will user attributes be used to author policies, or will groups also be needed? The subscription and data policies below illustrate the need for both groups and attributes to be imported from the IAM to enforce appropriate access controls:

   1. Subscription policy: Allow all users in the Marketing group to access data sources tagged Marketing.

   2. Data policy: Mask all columns tagged Location except for users with the attribute AccessLevel.Gold.

2. If your provider is not listed or does not support SCIM, reach out to your Immuta representative for guidance.

3. with SCIM enabled. Guides for specific providers are linked below.

Next steps

Once your IAM is configured, complete one of the following tasks:

Requirements

• An Immuta SaaS tenant is required to use Immuta's SCIM 2.0 feature.

• Users have to be an administrator in Okta to edit or add applications.

Supported features

The following Okta provisioning features are supported by Immuta:

• Import Users from Okta: Okta users who had previously been assigned to an Okta application can be imported to your Immuta tenant.

• Push users to Immuta: Okta users who are assigned to the Immuta application in Okta are automatically added as members to your Immuta tenant.

• Deactivate users in Immuta: Okta users who are unassigned from the Immuta application in Okta or are deleted or deactivated from Okta are automatically deactivated in your Immuta tenant.

• Push groups to Immuta: Groups and their members in Okta can be pushed to your Immuta tenant.

• Remove groups from Immuta: Groups in Okta are removed from your Immuta tenant when they are no longer mapped to your Immuta application in Okta.

• Map user attributes from Okta to Immuta: You can map user attributes between Okta and your Immuta tenant. The mapping will remain synced by detecting profile changes in Okta.

Configuration instructions

1 - Add SAML application in Okta

1. Log in to your Okta instance and click Applications in the menu in the left pane.

2. Click Browse App Catalog, and then search for and select Immuta.

3. Click Add.

4. In General Settings, opt to change the Application label. Then, click Next.

5. Click View Setup Instructions and complete the tutorial to configure the IAM in Immuta. Note: You will complete all steps outlined for the Immuta App Settings page except Test User Login. You cannot test the login or save the IAM configuration in Immuta until you have added yourself as a user to the application in Okta. These steps are outlined in the next section.

6. In the Okta console under Advanced Sign-on Settings, fill in the following fields.

   • Base URL (typically your Immuta tenant URL)

   • IAM ID (found on the Immuta App Settings page)

7. Click Done.

Attribute matching for SCIM

Attribute matching allows you to determine how to uniquely identify a user in Okta and match that user in Immuta at login and during provisioning. Immuta supports the following matching attributes in Okta:

• Users:

  • id

  • userName

  • email

  • displayName

  • emails[type eq "work"].value

• Groups

  • id

  • displayName

Using any other attribute in Okta as a matching attribute results in an error. See the Okta documentation for details about attribute matching and how to configure it.

2 - Add a user to the application

1. Click the Assignments tab.

2. Click Assign and then Assign to People.

3. Enter your name in the search field to filter results, and then click Assign.

4. Click Save and Go Back, and then click Done.

5. Return to the Immuta console and click Test User Login. Once this test passes, click Save.

3 - Configure Immuta to use SCIM external IAM

1. Navigate to the App Settings page in Immuta, and click the Add IAM button.

2. Complete the Display Name field and select SAML as your IAM type from the Identity Provider Type dropdown.

3. Adjust Default Permissions granted to users by selecting from the list in this dropdown menu, and then complete the required fields in the Client Options section.

4. Enable SCIM support for SAML by clicking the checkbox, which will generate a SCIM API Key. Validate that the usernames in your IAM match those in your data platform (Snowflake, Databricks, etc.). If they are incorrect in the IAM or the casing doesn't match, fix the data platform username in the identity provider before configuring SCIM in Immuta.

5. In the Profile Schema section, map attributes in SAML to automatically fill in a user's Immuta profile. Note: Fields that you specify in this schema will not be editable by users within Immuta.

6. Enable Sync groups from SAML to Immuta and Sync attributes from SAML to Immuta by selecting the checkboxes, and then click the Test Connection button.

7. Once the connection is successful, click the Test User Login button.

8. Before you save the configuration, store the SCIM information that displays on the Immuta App Settings page, as it will be used in subsequent steps.

4 - Update existing Okta application to enable SCIM

1. In Okta, navigate to your application and click the Provisioning tab.

2. Click Configure API Integration and then select the Enable API integration checkbox.

3. Fill in the following fields:

   • Base URL (found on the Immuta App Settings page as SCIM URL)

   • API Token (found on the Immuta App Settings page as SCIM Api Key)

4. Click Test API Credentials.

5. Once that test passes, click Save.

6. You will automatically navigate to the Provisioning tab. To make sure everything syncs as expected, select To App in the Settings pane, click Edit, and enable the following fields:

   • Create Users

   • Update User Attributes

   • Deactivate Users

7. Click Save.

Known issues and limitations

• Using the same group to assign users to Okta (groups added to the Okta Assignments tab) and to push groups and users to Immuta (groups added to the Okta Push Groups tab) is not supported. See the Okta troubleshooting guide for details.

• The Okta directory cannot be synced with Immuta's internal IAM (BIM). You must configure an external IAM in Immuta to push users and groups from Okta to Immuta.

• You should create a new Immuta IAM and a new Okta application for Immuta to set up the provisioning. An existing setup can cause discrepancies between the Okta directory and the app, leading to syncing failures.

• When making a GET request for a user, there are extra attributes in the response.

Additional tutorials

Manage users in Okta SCIM

Add users in Okta SCIM

1. Navigate to your application in Okta and click the Assignments tab.

2. Click Assign and then Assign to People.

3. Enter the name of the user you would like to add in the search field and click Assign.

4. Click Save and Go Back, and then click Done.

The user has been added to your application in Okta and displays as a user in Immuta under this external IAM.

Remove users from Okta SCIM

1. Click the delete icon next to the user you want to remove.

2. When prompted to make sure you want to delete this user, click OK.

This user is removed from your application in Okta and displays as disabled in Immuta under this external IAM.

Manage groups

Add users to groups

1. In Okta, navigate to your application and click on the Assignments tab.

2. Click on the name of the user whose groups you want to update.

3. Click on the Groups tab.

4. To add a new group, start to type the name of an existing group in the search field, and when it displays, click Add.

This group has been added to the user in Okta. It will also automatically appear in Immuta for the same user.

Remove users from groups

1. In Okta, navigate to your application and click the Assignments tab.

2. Click the name of the user whose groups you want to update, and then navigate to the Groups tab.

3. Click the delete icon next to the group you want to remove for this user.

This group has been removed from the user in Okta, and it will automatically be removed from this user in Immuta.

Manage attributes with Okta SCIM

Add Attributes to Users

1. In Okta, navigate to your application and click To App on the Provisioning tab.

2. Click the Go to Profile Editor button.

3. Click Add Attribute and fill in the following fields:

   • Data type (defaults to string).

   • Display name.

   • Variable name.

   • External namespace. This field has to be formatted using a special schema format (e.g., urn:ietf:params:scim:schemas:extension:enterprise:2.0:DEMOEXT). Copy this information; you will need it for Immuta configuration.

4. Click Save.

By default, the value for this attribute is empty. Follow the Adding Attribute Values section to add values.

Update the SCIM attribute schema in Immuta

1. In Immuta, navigate to the App Settings page and edit your SCIM configuration.

2. Scroll to the Attribute Schema section under Sync Attributes.

3. Click Add Attribute and complete the following fields:

   • SCIM Schema: found on the Okta SCIM attribute page

   • IAM Immuta Attribute Prefix: this can be anything you want

4. Click Test Connection and then Test User.

5. Save your changes.

Add attribute values

After adding attributes to users and updating the SCIM Attribute Schema in Immuta,

1. In Okta, navigate to the Assignments tab for your application and click the edit icon next to the user you want to update attributes for.

2. Scroll to the attribute you created and add a value in the textbox.

3. Save your changes.

Now that this attribute has been added to the user in Okta, it will automatically appear in Immuta for the same user.

Sync external usernames with Okta SCIM in Immuta

1. In Immuta, navigate to your Okta SCIM configuration on the App Settings page.

2. Under Sync attributes from SAML to Immuta, add an attribute for the field you would like to map to an external username.

3. Copy and paste the resulting attribute for the desired external username.

4. Click Test Connection and then Test User.

5. Save your changes.