A 4me provisioning flow failure occurs in Okta when the API token or Base URL that creates the API connection is invalid.

Resolve this issue by updating the Base URL and API token in the Okta Admin Console and retrying the failed tasks.

The following error appears in the Okta dashboard when the provisioning flow fails:

Automatic provisioning of user <user> to app 4me failed: Error while verifying if user <user> exists: Unauthorized. Errors reported by remote server

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Xurrent / 4me
• Provisioning

How is the 4me provisioning error resolved?

Update the Base URL and API token in the Okta Admin Console and retry the failed tasks:

1. Access the Okta Admin Console.
2. Navigate to Applications > 4me > Provisioning > Integration > Edit.
3. Enter the 4me System for Cross-domain Identity Management (SCIM) endpoint into the Base URL field.
4. Enter the 4me SCIM bearer token into the API Token field.
5. Select Test API Credentials, verify the successful connection, and select Save.
6. Navigate to Dashboard > Tasks.

7. Locate the failed task for the user and select Retry Selected.

Related References

• Xurrent / 4me Configuration Guide