Troubleshooting the Okta and Omnissa Access SCIM Integration

Use this information to troubleshoot some of the common errors that can occur with the Okta and Omnissa Access SCIM integration.

• Error: “Errors reported by remote server: Required user attributes:[DISTINGUISHEDNAME] are missing.”

  Solution: distinguishedName is set as a required attribute in Omnissa Access. In the Omnissa Access console Settings > User Attributes page, deselect the Required check box for the distinguishedName attribute.

• Error: “Errors reported by remote server: User creation is not supported for specified directory ID.”

  Solution: You are attempting to create a user in a directory that is not of type Other. Verify that while completing the prerequisites you did not use a domain that is used by another directory. It is possible that the domain was used for Just-in-Time (JIT) users. If so, you must create another directory of type Other with a unique domain.

• Error: “Errors reported by remote server: User domain name specified for the user resource doesn't belong to the directory.”

  Solution: The domain you configured in the attribute mapping in Okta does not match the domain for the directory created in Omnissa Access. Ensure that they match.

• Error: Automatic provisioning of user <username> to app Workspace ONE failed: Matching user not found.

  Solution: The Create Users and Deactivate Users settings are not enabled in the Provisioning tab of the Workspace ONE app. Go to the Provisioning tab, click Edit, and select the Enable check box for Create Users and Deactivate Users.

• Error: Groups in Omnissa Access have fewer users than groups in Okta

  Users might be missing from groups in Omnissa Access if they were not assigned to the Workspace ONE provisioning application in Okta before the group was pushed.

  Solution: Make sure that all the users that you want to provision to Omnissa Access are assigned to the Workspace ONE application first, before you push groups to Omnissa Access.