LogoLogo
Support Knowledge Articles
Public Knowledge BaseSupport Knowledge ArticlesPrerequisite Checklist HubSnowflakeSelf-Managed Articles
Support Knowledge Articles
Public Knowledge BaseSupport Knowledge ArticlesPrerequisite Checklist HubSnowflakeSelf-Managed Articles
  • Advanced Configuration
    • Deploying Immuta with a custom Certificate Authority or Trust Chain
    • Modifications require proper indentation
    • Adding an HTTP Proxy to Self-Managed Deployment
  • Audit
    • Altering the default audit trail record types and collection duration
    • API calls required to collect an audit trail
  • Backups
    • Azure Gov Backups fail due to incorrect Azure API URL
  • Data Sources
    • Health Tab: Trigger Detection button vs. Sync Data Policies
  • Identity Management
    • Entra ID - SCIM Configuration
      • Entra ID - Importing Users via SCIM
      • Entra ID - Importing Groups via SCIM
      • Entra ID - Importing Attributes via SCIM
      • Entra ID - Creating an attribute with toUpper or toLower
    • Attributes are not updated during initial create user payload via SCIM on Azure AD
    • Attempting to sign-in with AzureAD SSO fails with AADSTS75011
    • Attributes must be populated in Okta in order to be imported Immuta
    • Configuring a PingID IAM integration with Immuta
    • Configuring a SAML IAM when using an Immuta public URL
    • Configuring a SecureAuth integration with Immuta
    • Okta - SCIM Configuration
  • Projects
    • Attempts To Delete An Immuta Schema Project Fail
  • Snowflake
    • IP Address is not Allowed to Access Snowflake
  • Permissions
    • Can you assign ownership of a datasource based off of tags and/or groups?
  • Save Button Enablement
Powered by GitBook
On this page
  • Issue
  • Cause
  • Resolution
  1. Identity Management

Attributes must be populated in Okta in order to be imported Immuta

A user reported they were having issues bringing attributes into Immuta from Okta

PreviousAttempting to sign-in with AzureAD SSO fails with AADSTS75011NextConfiguring a PingID IAM integration with Immuta

Last updated 9 months ago

Issue

A user reported they were having issues bringing attributes into Immuta from Okta

Cause

Unpopulated attributes.

Resolution

Provided the user with , and step by step instructions and a demonstration of how to bring over attributes. It was found that majority of their attributes weren't mapped to a value and were unpopulated. In order to ensure attributes are imported into Immuta the following steps must take place:

  1. Create the attribute in Okta.

  2. Create the attribute mapping in Immuta.

  3. Populate the attribute in Okta.

documentation