Why does my scim/v2/Users API request timeout?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Why does my scim/v2/Users API request timeout?

L0 Member

When I try to make a get request to the scim/v2/Users endpoint, my request runs for > 5 minutes, even when I pass in a parameter of count=1. Does anyone have experience with the API and been able to requests Users and Groups data in a reasonable amount of time?

1 accepted solution

Accepted Solutions

Fundamentally, the SCIM web service requests are being performed against the tenant PVWA after being received by Identity. The performance discrepancies are likely a result of the individual PVWAs available resources, performance and configuration.

 

I see very good results from support cases related to this SCIM setup - you should absolutely open a case since there are backend settings that can contribute to a resolution.

 

To point you in a vague, general direction (open a support case!), I have seen issues with health checks being sent by the SCIM server to endpoints that don't exist leading to timeout issues, among other things. Similarly, adjusting the "UsePaginationToQueryUsers" setting in the config.json file can sometimes help here.

View solution in original post

4 REPLIES 4

L6 Presenter

Could you try removing the "/v2" from the URI?

 

Identity API reference: https://api-docs.cyberark.com/docs/identity-api-reference/scim/operations/list-users

L0 Member

Hello! Working with Ryan on the same issue here -- removing "/v2" speeds up the request for our own Customer / Tenant ID, but other Tenant IDs are still timing out. Is there a reason why different Tenant IDs would be experiencing different behavior?

Fundamentally, the SCIM web service requests are being performed against the tenant PVWA after being received by Identity. The performance discrepancies are likely a result of the individual PVWAs available resources, performance and configuration.

 

I see very good results from support cases related to this SCIM setup - you should absolutely open a case since there are backend settings that can contribute to a resolution.

 

To point you in a vague, general direction (open a support case!), I have seen issues with health checks being sent by the SCIM server to endpoints that don't exist leading to timeout issues, among other things. Similarly, adjusting the "UsePaginationToQueryUsers" setting in the config.json file can sometimes help here.

Thank you for the detailed answer here -- we will look towards opening support cases, then!

  • 1 accepted solution
  • 283 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!