<?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 Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve. in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320010#M19561</link>
    <description>&lt;P&gt;Scenario:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;B&gt;User A&lt;/B&gt; submits request&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;User B&lt;/B&gt; submits request&lt;/LI&gt;&lt;LI&gt;Both requests approved (Dual Control / Workflow)&lt;/LI&gt;&lt;LI&gt;User A retrieves password&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Password NOT rotated&lt;/B&gt; (since CPM not available)&lt;/LI&gt;&lt;LI&gt;The 7‑day request expires&lt;/LI&gt;&lt;LI&gt;User B may still try retrieving password (same old value)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;And your goal:&lt;/P&gt;&lt;P&gt;&lt;B&gt;Prevent User B from ever getting the same password User A retrieved — even after approval.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;And do this &lt;B&gt;without CPM&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 22 Jan 2026 03:37:16 GMT</pubDate>
    <dc:creator>dleo</dc:creator>
    <dc:date>2026-01-22T03:37:16Z</dc:date>
    <item>
      <title>Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320010#M19561</link>
      <description>&lt;P&gt;Scenario:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;B&gt;User A&lt;/B&gt; submits request&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;User B&lt;/B&gt; submits request&lt;/LI&gt;&lt;LI&gt;Both requests approved (Dual Control / Workflow)&lt;/LI&gt;&lt;LI&gt;User A retrieves password&lt;/LI&gt;&lt;LI&gt;&lt;B&gt;Password NOT rotated&lt;/B&gt; (since CPM not available)&lt;/LI&gt;&lt;LI&gt;The 7‑day request expires&lt;/LI&gt;&lt;LI&gt;User B may still try retrieving password (same old value)&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;And your goal:&lt;/P&gt;&lt;P&gt;&lt;B&gt;Prevent User B from ever getting the same password User A retrieved — even after approval.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;And do this &lt;B&gt;without CPM&lt;/B&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 03:37:16 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320010#M19561</guid>
      <dc:creator>dleo</dc:creator>
      <dc:date>2026-01-22T03:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320011#M19562</link>
      <description>&lt;P&gt;Hey @D Leo​&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can make the object exclusive so only 1 user at a time can use it. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is a section on this from the docs: https://docs.cyberark.com/pam-self-hosted/15.0/en/content/pasimp/accounts-check-out-and-check-in.htm?Highlight=exclusive&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm unsure if you can achieve this without the CPM involved, though. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;-Matt&lt;/P&gt;</description>
      <pubDate>Thu, 22 Jan 2026 12:52:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320011#M19562</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-01-22T12:52:53Z</dc:date>
    </item>
    <item>
      <title>Re: Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320012#M19563</link>
      <description>&lt;P&gt;As @Matt Jennison​&amp;nbsp;says - I'm not sure I understand how this workflow could function to achieve your goal without CPM being used to rotate the password. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let's extend your steps by considering two scenarios. In scenario 1 user A checks the account out, reads the password, and 2 days later checks it back in but does not change the password. User B now checks out the account and reads the password. For the next five days both both User A and User B know the password, so you have not achieved your goal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In scenarion 2 user A checks the account out, reads the password, and 2 days later changes the password on the target and in CyberArk and checks the account in. User B now checks out the account and reads the password. For the next five days both User A and User B know the password so you have not achieved your goal.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CPM is used to prevent administrators knowing the password for privileged accounts beyond the period of time privileged access is approved.&lt;/LI&gt;&lt;LI&gt;PSM is used to prevent administrators ever knowing the password for privileged accounts while still gaining access to targets during the period of time privileged access is approved.&lt;/LI&gt;&lt;LI&gt;SIA / SCA are used to prevent privileged accounts existing beyond the period of time privileged access is approved while still granting access during the period of time privileged access is approved.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Jan 2026 13:59:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320012#M19563</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2026-01-26T13:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320013#M19564</link>
      <description>&lt;P&gt;Thank you @Matt Jennison​&amp;nbsp;&amp;amp; @Jon Musker​&amp;nbsp;for your response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My objective is prevent User B from checking-out the password before the new password is stored. &lt;/P&gt;&lt;P&gt;Unforturnately, we have some unmanaged IDs (cannot onboard to CPM platforms) and CyberArk is automatically releasing the ID after CyberArk request expired - allowing User B to withdraw the same password.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks like there is no workaround to prevent automatic release.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jan 2026 01:32:52 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320013#M19564</guid>
      <dc:creator>dleo</dc:creator>
      <dc:date>2026-01-27T01:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: Can CyberArk Prevent another User B from ever getting the same password User A retrieved — even after approval. And do this without CPM. Password must be manually reset and store into CyberArk before User B can retrieve.</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320014#M19565</link>
      <description>&lt;P&gt;Enforce check-in/check-out exclusive&amp;nbsp;is Enabled. But CyberArk will still auto release the ID after Request expired.&lt;/P&gt;&lt;P&gt;Without CPM runing for that ID, passwords stay the same. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Would be great if CyberArk can check that there is a new password stored before releasing the ID. Unfortunately, it doesnt work this way.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Jan 2026 00:51:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/can-cyberark-prevent-another-user-b-from-ever-getting-the-same/m-p/1320014#M19565</guid>
      <dc:creator>dleo</dc:creator>
      <dc:date>2026-01-28T00:51:21Z</dc:date>
    </item>
  </channel>
</rss>

