- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
01-21-2026 07:37 PM
Scenario:
And your goal:
Prevent User B from ever getting the same password User A retrieved — even after approval.
And do this without CPM.
01-22-2026 04:52 AM
Hey @D Leo
You can make the object exclusive so only 1 user at a time can use it.
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
I'm unsure if you can achieve this without the CPM involved, though.
-Matt
01-22-2026 04:52 AM
Hey @D Leo
You can make the object exclusive so only 1 user at a time can use it.
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
I'm unsure if you can achieve this without the CPM involved, though.
-Matt
01-26-2026 05:59 AM
As @Matt Jennison says - I'm not sure I understand how this workflow could function to achieve your goal without CPM being used to rotate the password.
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.
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.
01-26-2026 05:32 PM
Thank you @Matt Jennison & @Jon Musker for your response.
My objective is prevent User B from checking-out the password before the new password is stored.
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.
Looks like there is no workaround to prevent automatic release.
01-27-2026 04:51 PM
Enforce check-in/check-out exclusive is Enabled. But CyberArk will still auto release the ID after Request expired.
Without CPM runing for that ID, passwords stay the same.
Would be great if CyberArk can check that there is a new password stored before releasing the ID. Unfortunately, it doesnt work this way.
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!

