You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use a 60-day password rotation schedule. We need the ability to change this rotation schedule for a single user. The use case is that we had to reveal the local administrator password to an end user to deal with an OS level issue. After use we would like to force a rotation. I'm familiar with other password management solutions that allow the admins to mark a password as "used" and then the system forces a password rotation. It would be nice if this could be performed Ad-hoc from the dashboard.
We have also looked at just changing the rotation schedule to the 3 days that is the application default. We have several thousand users and the work is that the Password/Secret version history will consume a lot of storage in the Key Vault. I believe the "older" version are kept for a period of one year. I haven't found anything on limiting the older versions either in number or lenght of time they are retained.
The text was updated successfully, but these errors were encountered:
We use a 60-day password rotation schedule. We need the ability to change this rotation schedule for a single user. The use case is that we had to reveal the local administrator password to an end user to deal with an OS level issue. After use we would like to force a rotation. I'm familiar with other password management solutions that allow the admins to mark a password as "used" and then the system forces a password rotation. It would be nice if this could be performed Ad-hoc from the dashboard.
We have also looked at just changing the rotation schedule to the 3 days that is the application default. We have several thousand users and the work is that the Password/Secret version history will consume a lot of storage in the Key Vault. I believe the "older" version are kept for a period of one year. I haven't found anything on limiting the older versions either in number or lenght of time they are retained.
The text was updated successfully, but these errors were encountered: