Hello Angel, Yes, you are correct. Just like Michael suggested yesterday, my ppolicy schema was not loaded. I had it in the system earlier, which added extra confusion. As per Michael's advice, I found [on my system] and loaded a ready-made ppolicy.ldif and there are no more configuration errors, for now. :)
Sincerely, Igor Shmukler On Tue, Mar 10, 2015 at 9:06 AM, Angel L. Mateo <[email protected]> wrote: > > El 09/03/15 a las 12:10, Igor Shmukler escribió: >> >> I also have an LDIF for default policy, added as: $ldapadd -x -D >> cn=admin,dc=example,dc=com -W -f default_ppolicy.ldif >> >> It contains: >> dn: ou=policies,dc=example,dc=com >> objectClass: top >> objectClass: organizationalUnit >> ou: policies >> >> dn: cn=ppolicy,ou=policies,dc=example,dc=com >> objectClass: top >> objectClass: device >> objectClass: pwdPolicyChecker >> objectClass: pwdPolicy >> cn: ppolicy >> pwdAttribute: userPassword > > > I think the problem is the pwdAttribute attribute in your ldif. > Although in examples is shown as you have, in my case I had to put the OID > of the userPassword, not the "userPassword" string. > > -- > Angel L. Mateo Martínez > Sección de Telemática > Área de Tecnologías de la Información > y las Comunicaciones Aplicadas (ATICA) > http://www.um.es/atica > Tfo: 868887590 > Fax: 868888337 >
