I am following up in hopes that maybe this was just missed the first time around. Is
anyone using a subtree password policy in a recent version of 389 and does it work?
On May 11, 2016, at 16:51, Morgan Jones
We are configuring password policy in 389 directory. We’re running what I believe is the
latest stable version form the Epel repository on CentOS 6:
[root@devldapm03 ~]# rpm -qa|grep 389
[morgan@devldapm03 ~]$ uname -a
2.6.32-573.26.1.el6.x86_64 #1 SMP Wed May 4 00:57:44 UTC
2016 x86_64 x86_64 x86_64 GNU/Linux
[morgan@devldapm03 ~]$ cat /etc/redhat-release
CentOS release 6.7 (Final)
I just did a yum update, rebooted and installed 389 anew.
The password policy works well if configured globally (from the Data node under
However when I attempt to create a subtree level policy
(Directory->domain->employees, right click Manage Password Policy->for subtree)
under ou=employees,dc=domain,dc=org the effect is as if there is no policy. If I
subsequently disable the subtree policy I cannot get the global policy to take over. In
fact the only way I’ve been able to get the global policy to work is to re-install from
I also tried command line configuration and was unable to get the policy working at all
though I have more confidence of my understanding of the process via the console.
We’ve tried different policy settings but for testing purposes I’m just setting a minimum
password length of 8 characters.
Is there something I’m missing?
389-users mailing list