Hi.
I have OpenLDAP 2.4.36 server grabbed from LTB project. I’ve noticed two issues, can anyone confirm the same behavior?
First - ACLs: to dn.base="" by users read to dn.subtree="ou=disabledaccounts,o=examples" by dn.base="cn=replicationmanager,o=example" read by * none to attrs=userPassword,shadowLastChange by dn.base="cn=replicationmanager,o=example" read by dn.base=„cn=radiussuperuser,o=example" read by anonymous auth by self write by * none [skipping few next less important rules]
Above ACL should NOT show user’s own password, right? But it shows in my environment..
Second: PwdMinLength in password policy does not work. I can easily set shorter password. Password policy in general works, for example it does not allow me to change password earlier than ‚pwdMinAge’.
Best regards, — Olo
Wiadomość napisana przez Aleksander Dzierżanowski olo@e-lista.pl w dniu 25 lis 2013, o godz. 20:15:
First - ACLs:
Sorry for first question, as I can see in docs write access gives automatically read access. I was not aware of this. — Olo
For userPassword "by self write" implies the ability to read as well, try "by self =xw" if you want to be able to write to userPassword without being able to view it.
On Mon, Nov 25, 2013 at 2:15 PM, Aleksander Dzierżanowski olo@e-lista.plwrote:
Hi.
I have OpenLDAP 2.4.36 server grabbed from LTB project. I've noticed two issues, can anyone confirm the same behavior?
First - ACLs: to dn.base="" by users read to dn.subtree="ou=disabledaccounts,o=examples" by dn.base="cn=replicationmanager,o=example" read by * none to attrs=userPassword,shadowLastChange by dn.base="cn=replicationmanager,o=example" read by dn.base="cn=radiussuperuser,o=example" read by anonymous auth by self write by * none [skipping few next less important rules]
Above ACL should NOT show user's own password, right? But it shows in my environment..
Second: PwdMinLength in password policy does not work. I can easily set shorter password. Password policy in general works, for example it does not allow me to change password earlier than 'pwdMinAge'.
Best regards,
Olo
REMOVE ME
At 2013-11-26 03:47:27,"Michael Proto" michael.proto@tstllc.net wrote:
For userPassword "by self write" implies the ability to read as well, try "by self =xw" if you want to be able to write to userPassword without being able to view it.
On Mon, Nov 25, 2013 at 2:15 PM, Aleksander Dzierżanowski olo@e-lista.pl wrote: Hi.
I have OpenLDAP 2.4.36 server grabbed from LTB project. I’ve noticed two issues, can anyone confirm the same behavior?
First - ACLs: to dn.base="" by users read to dn.subtree="ou=disabledaccounts,o=examples" by dn.base="cn=replicationmanager,o=example" read by * none to attrs=userPassword,shadowLastChange by dn.base="cn=replicationmanager,o=example" read by dn.base=„cn=radiussuperuser,o=example" read by anonymous auth by self write by * none [skipping few next less important rules]
Above ACL should NOT show user’s own password, right? But it shows in my environment..
Second: PwdMinLength in password policy does not work. I can easily set shorter password. Password policy in general works, for example it does not allow me to change password earlier than ‚pwdMinAge’.
Best regards, — Olo
For the first question, Michael already answer you
For the second, could you give us more information, for example, how do you modify the password. I don't think so, but to remove any doubt, do you modify the password with a ldapmodify request on the userpassword? or with the extended operation to modify password which will follow the ppolicy constraints (which ldapmodify don't take into account)
On Tue, Nov 26, 2013 at 9:02 AM, mahao_boy mahao_boy@163.com wrote:
REMOVE ME
At 2013-11-26 03:47:27,"Michael Proto" michael.proto@tstllc.net wrote:
For userPassword "by self write" implies the ability to read as well, try "by self =xw" if you want to be able to write to userPassword without being able to view it.
On Mon, Nov 25, 2013 at 2:15 PM, Aleksander Dzierżanowski olo@e-lista.plwrote:
Hi.
I have OpenLDAP 2.4.36 server grabbed from LTB project. I've noticed two issues, can anyone confirm the same behavior?
First - ACLs: to dn.base="" by users read to dn.subtree="ou=disabledaccounts,o=examples" by dn.base="cn=replicationmanager,o=example" read by * none to attrs=userPassword,shadowLastChange by dn.base="cn=replicationmanager,o=example" read by dn.base="cn=radiussuperuser,o=example" read by anonymous auth by self write by * none [skipping few next less important rules]
Above ACL should NOT show user's own password, right? But it shows in my environment..
Second: PwdMinLength in password policy does not work. I can easily set shorter password. Password policy in general works, for example it does not allow me to change password earlier than 'pwdMinAge'.
Best regards,
Olo
2013/11/26 Esteban Pereira esteban.pereira@gepsit.fr:
For the first question, Michael already answer you
For the second, could you give us more information, for example, how do you modify the password. I don't think so, but to remove any doubt, do you modify the password with a ldapmodify request on the userpassword? or with the extended operation to modify password which will follow the ppolicy constraints (which ldapmodify don't take into account)
Password policy works with ldapmodify and extended password modification operation.
If the min length constraint does not work, it may be because you are sending to LDAP the SSHA encoded value in modification. In this case, the password policy overlay cannot check the size.
Other point, the password policy is bypassed by the rootdn. You have to change the password with another account.
Clément.
Thank you Esteban for your reply.
I was missing pwdCheckQuality attribute in pwpolicy, which is mandatory to set - if not, length checks are not performed. Default value (if not set) for pwdCheckQuality in my opinion should be set to 1. Otherwise presence of pwdMinLength in policy can be confusing.
Best regards,
Wiadomość napisana przez Esteban Pereira esteban.pereira@gepsit.fr w dniu 26 lis 2013, o godz. 09:59:
For the first question, Michael already answer you
For the second, could you give us more information, for example, how do you modify the password. I don't think so, but to remove any doubt, do you modify the password with a ldapmodify request on the userpassword? or with the extended operation to modify password which will follow the ppolicy constraints (which ldapmodify don't take into account)
On Tue, Nov 26, 2013 at 9:02 AM, mahao_boy mahao_boy@163.com wrote: REMOVE ME
At 2013-11-26 03:47:27,"Michael Proto" michael.proto@tstllc.net wrote: For userPassword "by self write" implies the ability to read as well, try "by self =xw" if you want to be able to write to userPassword without being able to view it.
On Mon, Nov 25, 2013 at 2:15 PM, Aleksander Dzierżanowski olo@e-lista.pl wrote: Hi.
I have OpenLDAP 2.4.36 server grabbed from LTB project. I’ve noticed two issues, can anyone confirm the same behavior?
First - ACLs: to dn.base="" by users read to dn.subtree="ou=disabledaccounts,o=examples" by dn.base="cn=replicationmanager,o=example" read by * none to attrs=userPassword,shadowLastChange by dn.base="cn=replicationmanager,o=example" read by dn.base=„cn=radiussuperuser,o=example" read by anonymous auth by self write by * none [skipping few next less important rules]
Above ACL should NOT show user’s own password, right? But it shows in my environment..
Second: PwdMinLength in password policy does not work. I can easily set shorter password. Password policy in general works, for example it does not allow me to change password earlier than ‚pwdMinAge’.
Best regards, — Olo
2013/11/26 Aleksander Dzierżanowski olo@e-lista.pl:
Thank you Esteban for your reply.
I was missing pwdCheckQuality attribute in pwpolicy, which is mandatory to set - if not, length checks are not performed. Default value (if not set) for pwdCheckQuality in my opinion should be set to 1. Otherwise presence of pwdMinLength in policy can be confusing.
Set it to 2 if you want to reject SSHA passwords for which min length can not be checked.
Clément.
openldap-technical@openldap.org