Skip to content

Troubleshooting

If you encounter any of the following issues or errors, SailPoint recommends that you follow the guidance provided below to resolve the error before contacting SailPoint Support.

For issues or errors that are not addressed in this connector guide, refer to the following resources for troubleshooting information:

Account Create Succeeds; Group Entitlement Add Fails with ObjectNotFoundException (HTTP 404)

Account creation succeeds, but adding a group entitlement fails with the following error:

[ ObjectNotFoundException ] [ Error details ] Resource not found

The connector assigns groups after it creates the user. It first sends POST /admin/v1/users, then sends POST /admin/v1/groups/{groupId}/users once for each group. Groups are not included in the create request body.

Resolution - If POST /users succeeds with HTTP 201 and POST /groups/{groupId}/users fails with HTTP 404, complete the following:

  1. Confirm in the CCG logs that the HTTP 404 occurs on POST /groups/{groupId}/users, not on POST /users.
  2. Verify that the group exists by sending GET /admin/v1/groups/{groupId} with the connector OAuth client. If the GET request succeeds, the group ID is valid.
  3. Verify that the service account has permission for POST /groups/{groupId}/users. Refer to Required Permissions for more information.
  4. If the GET request succeeds but the POST membership request returns HTTP 404, confirm with Guidewire that the membership API is enabled for your tenant and group types.
  5. Rerun provisioning. The CCG logs should show HTTP 201 on user create, then success on each group membership call.

Documentation Feedback

Feedback is provided as an informational resource only and does not form part of SailPoint’s official product documentation. SailPoint does not warrant or make any guarantees about the feedback (including without limitation as to its accuracy, relevance, or reliability). All feedback is subject to the terms set forth at https://developer.sailpoint.com/discuss/tos.