I saw this in the ppolicy pages but was unsure of how to use it? I understand that I can use pwdCheckModule and even how to turn it on, but I am uncertain as to how to actually tell it that we want to have for example, one upper case, one lower case and one numeral. Has anybody done that? Thanks, Sara Kline -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Tuesday, May 01, 2012 4:36 PM To: Kline, Sara; openldap-technical(a)openldap.org Subject: Re: Tightening up ppolicy --On Tuesday, May 01, 2012 4:20 PM -0700 "Kline, Sara" <SKline(a)tnsi.com&gt; wrote: <http://www.openldap.org/software/man.cgi?query=slapo-ppolicy&apropos=... pwdCheckModule This attribute names a user-defined loadable module that must instanti- ate the check_password() function. This function will be called to further check a new password if pwdCheckQuality is set to one (1) or two (2), after all of the built-in password compliance checks have been passed. This function will be called according to this function proto- type: int check_password (char *pPasswd, char **ppErrStr, Entry *pEntry); The pPasswd parameter contains the clear-text user password, the ppErrStr parameter contains a double pointer that allows the function to return human-readable details about any error it encounters. The optional pEntry parameter, if non-NULL, carries a pointer to the entry whose password is being checked. If ppErrStr is NULL, then funcName must NOT attempt to use it/them. A return value of LDAP_SUCCESS from the called function indicates that the password is ok, any other value indicates that the password is unacceptable. If the password is unac- ceptable, the server will return an error to the client, and ppErrStr may be used to return a human-readable textual explanation of the error. The error string must be dynamically allocated as it will be free()'d by slapd. ( 1.3.6.1.4.1.4754.1.99.1 NAME 'pwdCheckModule' EQUALITY caseExactIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 SINGLE-VALUE ) Note: The user-defined loadable module named by pwdCheckModule must be in slapd's standard executable search PATH. Note: pwdCheckModule is a non-standard extension to the LDAP password policy proposal. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Services. Any unauthorised review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

I am not a programmer. I am just starting to learn Perl, but am not much beyond Hello World. Does anyone have an example that I could work from? I have some very rudimentary programming skills in a few languages but I have not found any examples online thus far that look like what I need. Thanks, Sara Kline -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Tuesday, May 01, 2012 4:42 PM To: Kline, Sara; openldap-technical(a)openldap.org Subject: RE: Tightening up ppolicy --On Tuesday, May 01, 2012 4:39 PM -0700 "Kline, Sara" <SKline(a)tnsi.com&gt; wrote: You write a checking module, and in that module, you do the strength tests that you require. As noted in the text from the man page. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration This e-mail message is for the sole use of the intended recipient(s)and may contain confidential and privileged information of Transaction Network Services. Any unauthorised review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

On Tue, 1 May 2012, Kline, Sara wrote: This project is licensed under the OpenLDAP Public License (so it's hopefully compatible with your organization's philosophy if you're already using slapd) and might be a starting point: http://open.calivia.com/projects/openldap blog entry with config file details: http://www.calivia.com/blog/mike/openldap-check_password-password-policy-... Another example is found in OpenLDAP ITS #6884. I've used neither of these options and cannot vouch for (nor against) them in any way.