LogoLogo
Public Knowledge Base
Public Knowledge BaseSupport Knowledge ArticlesPrerequisite Checklist HubSnowflakeSelf-Managed Articles
Public Knowledge Base
Public Knowledge BaseSupport Knowledge ArticlesPrerequisite Checklist HubSnowflakeSelf-Managed Articles
  • Self-hosted Immuta
    • Official Immuta Self-Managed Deployment Documentation
    • What's new in 2024.2?
    • Deployment Options
      • AWS Immuta Deployment
      • Azure Immuta Deployment
      • In-cluster PostgreSQL using Crunchydata
      • In-cluster Elasticsearch using Elastic Cloud on Kubernetes (ECK)
      • Production Linkerd with AWS Private CA issuer
      • Deploying Linkerd via Open Source Linkerd
      • Deploying Linkerd Service Mesh via Buoyant Enterprise for Linkerd
      • Uninstalling Linkerd
      • Upgrading to Immuta 2024.2 LTS
      • LTS Upgrade via Legacy Chart
      • Legacy Audit - no Elasticsearch
      • Temporal with RDS
      • Setting Up OpenSearch User Pemissions
    • Air gapped installations
      • Immuta Installation on k3s in Air Gapped environment
      • Air-gapped Installation Artifact Transfer
  • Excessive failed jobs in pgboss impacting system performance
  • Example Trino installation via Open Source Helm Chart
  • Immuta Installation on Self Managed Infrastructure Overview
  • Repeatable k3s stack deployment on AWS EC2
  • Trino OAuth2 and JWT via Okta
  • Copy of Okta Attribute Mapping
Powered by GitBook
On this page
  • Adding the Attribute to the Okta Profile
  • Validating the attribute in the application (Okta)
  • Immuta Updates
  • Update SCIM integration with new API Key
  • Force Sync

Okta Attribute Mapping

Last updated 4 days ago

The goal is to add a user attribute to the Application profile for an Immuta Application in Okta and then update the IAM configuration in Immuta to accept the new attribute.

Adding the Attribute to the Okta Profile

  • As an admin go to Directory -> Profile Editor

  • Find the application profile for the Immuta application in the list and click the Profile User link

  • In the Attributes Section click Add Attribute

  • On the Add Attribute Modal:

    • Set a display name, variable name and external namespace

    • Click Save

  • Click Mappings

  • Select Okta User to AppName

  • Select an attribute to map to the newly created application attribute

  • Click Save Mappings

  • Click Apply Updates Now

Validating the attribute in the application (Okta)

  • Navigate to Applications -> Applications

  • Click Assignements

  • Click the icon next to an assigned user

  • Observe the attribute on their assignment page

Immuta Updates

  • In Immuta Remove the IAM if it exists

  • Click Save

  • Readd the IAM and note the new SCIM API key

  • Map the external namespace specified earlier to an arbitrary Immuta prefix

  • Click Test Connection

  • Click Test User Login

  • Click Save

Update SCIM integration with new API Key

  • Click Provisioning

  • Click Integration

  • Click Edit

  • Update the API Token

  • Click Test API Credentials

  • Click Save

Force Sync

  • On the Okta Application page click Provisioning -> To Appand Force Sync

🖊️