Okta SCIM - Default Attributes

Understanding Okta SCIM Default Attributes

When configuring your Okta SCIM application, it is critical that you do not delete any of the default attributes. Removing these attributes directly from the Okta application will cause critical synchronization failures, preventing successful user provisioning, deprovisioning, and routine user attribute updates.

Attribute Mapping Table Guide

Please reference the table below for a complete list of the required application attributes.

• Starred Rows (*): These rows indicate attributes that are required by the application and represent where the platform stores essential user information.

• The userName Attribute (**): This is a strict requirement for the application to function and must remain mapped to the user's primary identifier.

• Remapping Allowed: With the exception of userName, the attributes in the starred rows can be safely remapped to send different user values from Okta if your organizational structure requires it.

How to Handle Unwanted Attributes (Syncing Null Values)

If there are specific default values in the table that you do not wish to synchronize with the platform, do not delete the attribute.

Instead, you must remap the unwanted attribute to sync a Null value.

⚠️ Critical Exceptions: You cannot sync Null values for core identity fields. Ensure that valid data mappings are always retained for the following platform attributes:

• First Name

• Last Name

• Email