Common problems with user provisioning

This article provides answers to most common issues related to automatic user provisioning (SCIM). Unless otherwise noted, all items below are applicable to all Identity Providers.

Names cannot contain brackets <>(){}[]

Due to security reasons, user's first name and last name cannot contain any bracket characters. If at all possible, avoid using bracket characters in first name and last name data in Azure AD.

 

User's department was first provisioned as "dept123" but it was recently changed to "Dept123". However, the update doesn't show up in Hoxhunt. What's going on?

SCIM provisioning doesn't distinguish between small case and capital case letters. In this above example, SCIM considers that user's department data hasn't changed, so it doesn't send a change request to Hoxhunt.

Using provision-on-demand or restarting the provisioning doesn't help. Please contact Hoxhunt Support to have the data updated.

After setting up SCIM, we have been seeing duplicate user accounts. What's going on?

Most likely you have a configuration mismatch between the user attribute mappings of SSO and SCIM.

You might also have configured SCIM to provision users with their UPN (principal name) instead of email address.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request