Is it possible to enforce a user logoff on target servers before initiating (manual/scheduled) password rotation?

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

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Is it possible to enforce a user logoff on target servers before initiating (manual/scheduled) password rotation?

L2 Linker
1 accepted solution

Accepted Solutions

L7 Applicator

Hi @RR Anthony Alca​ 

 

You can look at the following two parameters.

 

 

Exclusive Access: When enforced, the password is changed immediately after the user releases the account (checks it in). This essentially ensures the rotation happens after the session is complete.

 

MinValidityPeriod: This parameter, often used with Exclusive Access or One-Time Passwords, defines the minimum time (in minutes) an account must remain with the new password before the CPM is allowed to change it again. This is typically used to ensure the user's session is over before a subsequent change.

 

If you want to enforce at the target server end, you can configure operating system settings to automatically log off or disconnect idle sessions after a short period. It is not a CyberArk feature, but it supports the goal of ensuring the account is available for rotation.

View solution in original post

5 REPLIES 5

L4 Transporter

Hi @RR Anthony Alca​ ,

 

I am not sure about the feasibility of this.

 

However, if you are worried about rotation failures, you can set up password rotations to be executed only in the predefined off-peak hours. For that, you have to define 'FromHour' and 'ToHour' parameters within the platform.

 

Field_Content_versions_oct20__068Vy00000zKR7NIAW.png 

L7 Applicator

Hi @RR Anthony Alca​ 

 

You can look at the following two parameters.

 

 

Exclusive Access: When enforced, the password is changed immediately after the user releases the account (checks it in). This essentially ensures the rotation happens after the session is complete.

 

MinValidityPeriod: This parameter, often used with Exclusive Access or One-Time Passwords, defines the minimum time (in minutes) an account must remain with the new password before the CPM is allowed to change it again. This is typically used to ensure the user's session is over before a subsequent change.

 

If you want to enforce at the target server end, you can configure operating system settings to automatically log off or disconnect idle sessions after a short period. It is not a CyberArk feature, but it supports the goal of ensuring the account is available for rotation.

Hello @Uditha Arunasiri​

 

Thank you. Will check on this.

Hello @Malhar Vora​ 

 

Thank you. Will check on this too!

L4 Transporter

Hi @RR Anthony Alca​ 

 

It seems that Mahlar provided an answer to your question. Could you kindly let us know if this solution helped?

If so, please mark the answer as 'Select as Best' to assist other community members.

 

Thank you, Omri

  • 1 accepted solution
  • 141 Views
  • 5 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!