Okta Egnyte SCIM 2.0 Push Group Error: User Does Not Exist

Egnyte SCIM 2.0 push group fails with the following error visible in the Okta dashboard:

Unable to update Group Push mapping target App group XXXXX: Error while updating user group membership for group XXXXX: Bad Request. Errors reported by remote server: constraint violations: EgnyteConstraintViolationImpl{interpolatedMessage='User (XXXXX) does not exist', propertyPath=, messageTemplate='{user.not.found}'}, EgnyteConstraintViolationImpl{interpolatedMessage='User (XXXXX) does not exist', propertyPath=, messageTemplate='{user.not.found}'}...

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Egnyte System for Cross-domain Identity Management (SCIM) 2.0
• Provisioning
• Group Push

The group push fails because Okta cannot find specific users associated with the provided ID in the target application, as indicated in the Okta System Log error message.

How is the Egnyte SCIM 2.0 push group error resolved?

Validate the user accounts in the affected push group and retry the group push in the Okta Admin Console.

1. Verify that all users in the group exist in the Egnyte SCIM 2.0 application. Okta requires a pushed user to be active, assigned to the application, and part of the Okta pushed group. The target application requires the user to be provisioned and active.
2. Validate the following conditions for the users of the affected push group:
   • The user has an active account on the Egnyte SCIM 2.0 side.
   • The username on the Okta application assignment matches the value in the Egnyte SCIM 2.0 application.
   • The external ID on the Okta application assignment matches the value in the Egnyte SCIM 2.0 application.
   • The user account remains unchanged on the Egnyte SCIM 2.0 side.
3. Verify successful provisioning of all users to Egnyte SCIM 2.0.
4. Navigate to Applications > Applications in the Okta Admin Console.
5. Select the Egnyte SCIM 2.0 application.
6. Go to the Push Groups tab.
7. Attempt the group push again.