<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Why does my scim/v2/Users API request timeout? in Workforce Identity Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418822#M2356</link>
    <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
    <pubDate>Tue, 18 Mar 2025 15:29:36 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-03-18T15:29:36Z</dc:date>
    <item>
      <title>Why does my scim/v2/Users API request timeout?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418819#M2353</link>
      <description>&lt;P&gt;When I try to make a get request to the scim/v2/Users endpoint, my request runs for &amp;gt; 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?&lt;/P&gt;</description>
      <pubDate>Fri, 14 Mar 2025 19:37:18 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418819#M2353</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-14T19:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my scim/v2/Users API request timeout?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418820#M2354</link>
      <description>&lt;P&gt;Could you try removing the "/v2" from the URI?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Identity API reference: https://api-docs.cyberark.com/docs/identity-api-reference/scim/operations/list-users&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 15:59:24 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418820#M2354</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-17T15:59:24Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my scim/v2/Users API request timeout?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418821#M2355</link>
      <description>&lt;P&gt;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? &lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 14:54:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418821#M2355</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-18T14:54:13Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my scim/v2/Users API request timeout?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418822#M2356</link>
      <description>&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 15:29:36 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418822#M2356</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-18T15:29:36Z</dc:date>
    </item>
    <item>
      <title>Re: Why does my scim/v2/Users API request timeout?</title>
      <link>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418823#M2357</link>
      <description>&lt;P&gt;Thank you for the detailed answer here -- we will look towards opening support cases, then!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 15:36:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/workforce-identity-discussions/why-does-my-scim-v2-users-api-request-timeout/m-p/1418823#M2357</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-03-18T15:36:54Z</dc:date>
    </item>
  </channel>
</rss>

