<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content

Assigning a New User via a SCIM 2.0 Gives the Error: "Automatic provisioning of user: Invalid externalNamespace"

API Access Management

Overview

The purpose of this article is to provide a resolution for the SCIM 2.0 error:

Automatic provisioning of user {USER_NAME} to app {APP_NAME} failed: Error while creating user: Invalid externalNamespace

error 

 

Applies To

  • SCIM 2.0
  • Provisioning
  • Invalid externalNamespace

Cause

This issue might occur when creating a custom attribute in the SCIM app, such as the following, where the External namespace (Schema) is not set to the correct urn. Below the namespace is just the attribute name, 'test_er'.

attributes 

Solution

Instead, create a variable in the SCIM extension namespace (urn:ietf:params:scim:schemas:extension:) as below.

attributes 

NOTE: The best practice for the full schema URI depends on the custom schema/attribute being used, as mentioned in this RFC.

Loading
Assigning a New User via a SCIM 2.0 Gives the Error: "Automatic provisioning of user: Invalid externalNamespace" | Okta Support