Hi Cenk,
Yes this can be done by first locking the entry, and then setting
passwordLockoutDuration to the time (in seconds) into the future you
want it to unlock. So it's not a nice date you can use, but the value
can still be calculated
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11/html/administration_guide/managing_the_password_policy-configuring_the_account_lockout_policy#configuring_the_account_lockout_policy_using_the_command_line
HTH,
Mark
On 9/29/23 11:40 AM, Cenk Y. wrote:
Hello,
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?
Thanks
Cenk
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
