A custom schema attribute for a provisioning-enabled application is not sent as part of a user's provisioning request.

The attribute has been correctly mapped from the Okta UD.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Provisioning Enabled Applications

Check in Profile Editor if the attribute doesn't have a namespace associated with it.

Attributes without a proper namespace will not be included in provisioning messages. A common cause is that the attribute was created prior to enabling provisioning for the application.

Verify that provisioning is enabled for the application before creating the required custom attributes. Once enabled, the namespace field will be available for any new attributes created.

To update an existing attribute without a namespace, either delete it from the Admin Dashboard and create it again, or use the Management API to update it.

To use the management API

• Make a GET request to get the application user schema.
• Copy the response and use it to create a message for a POST request to update the application user schema.
• For any attribute that requires a namespace, add the two properties below to the custom attribute, each with the appropriate value. 
  • "externalName": "custom1"
  • "externalNamespace": "urn:ietf:params:scim:schemas:custom:Space"
• Once sent the Admin Dashboard will display the new properties

...
"custom1": {
  "title": "Custom Attribute",
  "description": "Custom Attribute",
  "type": "string",
  "externalName": "custom1",
  "externalNamespace": "urn:ietf:params:scim:schemas:custom:Space",
  "scope": "SELF",
  "master": {
      type": "PROFILE_MASTER"
   }
},
...