Friday, September 29, 2023

[389-users] Setting "lock" time of an account in the future


We are running 389-ds-base.2.2.7 .

While creating accounts, sometimes we know until when they need to be active. Is there a way to manually set a "expiration date" for the account, so after that date nsAccount is set to true?

Having gone through rhds and 389-ds pages, it seems it's only possible to create a policy to deactivate accounts after an inactivity limit.

I can always create a mechanism myself (such as adding a new attribute and checking it by a cron job ...) , but I want to see if there is a native way to do this?


No comments:

Post a Comment