<?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>article SCIM - Why the SCIM installer creates the REST API users consuming EPVUser licenses in the Vault? in PAM Self-Hosted Articles</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/scim-why-the-scim-installer-creates-the-rest-api-users-consuming/ta-p/1427890</link>
    <description>&lt;H3&gt;Question&lt;/H3&gt;
Why the SCIM installer creates the REST API users consuming EPVUser licenses in the Vault?

&lt;H3&gt;Answer&lt;/H3&gt;
By design, when the SCIM installer creates a REST API user, 'Sailpoint-user' for example, an EPVUser account is also created in the Vault.&lt;BR /&gt;&lt;BR /&gt;The REST API authentication in SCIM validates the credentials with the respective password object stored in the 'SCIM Config' safe, 'SailPoint-account' for example, the EPVUser account in the Vault is not being used at all by this process.&lt;BR /&gt;&lt;BR /&gt;Despite the EPVUser account is not being used by the REST API authentication process, Idira does not officially support removing, disabling or changing these EPVUser accounts in the Vault.&lt;BR /&gt;&lt;BR /&gt;If it's necessary to free up EPVUser license slots by SCIM, it's recommended to plan using OAUTH2 authentication on SCIM. Consider contacting your Idira account representative if any licensing issue arises.</description>
    <pubDate>Thu, 05 Nov 2026 20:07:58 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-11-05T20:07:58Z</dc:date>
    <item>
      <title>SCIM - Why the SCIM installer creates the REST API users consuming EPVUser licenses in the Vault?</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/scim-why-the-scim-installer-creates-the-rest-api-users-consuming/ta-p/1427890</link>
      <description>&lt;H3&gt;Question&lt;/H3&gt;
Why the SCIM installer creates the REST API users consuming EPVUser licenses in the Vault?

&lt;H3&gt;Answer&lt;/H3&gt;
By design, when the SCIM installer creates a REST API user, 'Sailpoint-user' for example, an EPVUser account is also created in the Vault.&lt;BR /&gt;&lt;BR /&gt;The REST API authentication in SCIM validates the credentials with the respective password object stored in the 'SCIM Config' safe, 'SailPoint-account' for example, the EPVUser account in the Vault is not being used at all by this process.&lt;BR /&gt;&lt;BR /&gt;Despite the EPVUser account is not being used by the REST API authentication process, Idira does not officially support removing, disabling or changing these EPVUser accounts in the Vault.&lt;BR /&gt;&lt;BR /&gt;If it's necessary to free up EPVUser license slots by SCIM, it's recommended to plan using OAUTH2 authentication on SCIM. Consider contacting your Idira account representative if any licensing issue arises.</description>
      <pubDate>Thu, 05 Nov 2026 20:07:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-articles/scim-why-the-scim-installer-creates-the-rest-api-users-consuming/ta-p/1427890</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-11-05T20:07:58Z</dc:date>
    </item>
  </channel>
</rss>

