Hey there,
I think that you also need:
pwdOTPValidFromTime
This way an admin can pre-configure all the OTP's and they only "become valid
from" that time frame. IE think university enrollment. You can configure all
the OTP's a month before, and they become valid at a specific datetime.
I
Hi team,
I've updated the contribution docs as I've tried to remove the confusion :)
https://github.com/mreynolds389/389wiki/pull/54/files
https://www.port389.org/docs/389ds/contributing.html
https://www.port389.org/docs/389ds/development/building.html
Hope that helps,
Simon
On Tue, Feb 23,
Hi,
I wrote a small design [1] about OTP password policy that I would like
to start implementing.
Comments are welcome
[1] https://www.port389.org/docs/389ds/design/otp-password-policy.html
best regards
thierry
___
389-devel mailing list --
https://fedorapeople.org/groups/389ds/ci/nightly/2021/03/22/report-389-ds-base-2.0.3-20210322git72726e42b.fc33.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to