An invalid external namespace property configured for an attribute in Okta causes an application assignment error during user provisioning. Deleting the invalid attribute and re-adding it with the correct external namespace resolves the issue. When a new user is assigned to a System for Cross-domain Identity Management (SCIM) application, Okta returns the following application assignment error:

Invalid externalNamespace

If the task is retried from the Admin Console, Okta successfully provisions the user without further errors.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Integration Network (OIN)
• System for Cross-domain Identity Management (SCIM) Application Template
• Universal Directory

The External Namespace property configured for the attribute in Okta does not match a supported namespace. The following external namespaces are supported by SCIM 2.0:

• urn:ietf:params:scim:schemas:core:2.0:User
• urn:ietf:params:scim:schemas:extension:enterprise:2.0:User

How is the "Invalid externalNamespace" error resolved?

Locate the SCIM application in the Profile Editor, delete the attribute with the invalid external namespace, and re-add the attribute with the correct external namespace by following these steps.

1. In the Okta Admin Console, navigate to Directory > Profile Editor, and select the SCIM application.
2. Select Profile.
3. Delete any attributes that have an invalid External namespace property associated with them.
   • Okta displays a prompt to remove the attribute from any mappings where it is referenced.
4. Re-add any attributes deleted in Step 3, and configure the correct External namespace.
   • For examples regarding external namespaces, review the SCIM Protocol or consult with the application developer to confirm the correct values.
5. Select Save Attribute.

The following image displays an example of an attribute named "costCenter" with a valid External Namespace.

Related References

• Okta and SCIM Version 2.0
• Okta and SCIM Version 1.1