Fri, 10 Apr 2026 14:48:30 +0000 https://bugs.horde.org/ticket/6012 Password expiration for Sun/Fedora Directory Server Fedora and Sun Directory Server uses a special operational attribute to record password expiration date. I submit a patch to use this attribute to warn the user about password expiration. This solution is not perfect, because: - password policy shoul be read from LDAP server instead of Horde configuration - Fedora/Sun Directory Server provide a grace period in which you can authenticate after expiration; in this time your messages present a negative number of remaining days. Cheers, Marco. Sat, 15 Dec 2007 12:36:33 +0000 https://bugs.horde.org/ticket/6012#t39940 I'm not sure why this would be in the smbldap driver, instead of the regular one? Sat, 15 Dec 2007 18:53:10 +0000 https://bugs.horde.org/ticket/6012#t39946 Sorry, I've some trouble in matching my system with your bugtrak service... The right patch is this and it is for lib/Horde/Auth/ldap.php, not for the password changer driver. Sun, 16 Dec 2007 13:10:55 +0000 https://bugs.horde.org/ticket/6012#t39964 Does specifying the list of attributes to fetch cause any problems if those attributes don't exist? Please avoid code for "shouldn't happen" situations. If a specific potential fault is being protected against, the comment should indicate that. Should it really be a login failure if there's bad data in this field? Also, please use pcre (preg_match) instead of ereg in all Horde code - it's much faster. If you could take a quick read through horde/docs/CODING_STANDARDS that would be wonderful, for this or future contributions, but I can fix this patch (whitespace mostly) as it's small. Mon, 17 Dec 2007 04:18:50 +0000 https://bugs.horde.org/ticket/6012#t39987 > Does specifying the list of attributes to fetch cause any problems if > those attributes don't exist? According to RFC 2251 if "there are attribute descriptions in the list which are not recognized, they are ignored by the server." However, I test the code with OpenLDAP and Fedora DS without trouble. > Please avoid code for "shouldn't happen" situations. If a specific > potential fault is being protected against, the comment should > indicate that. Should it really be a login failure if there's bad > data in this field? You are right. I think as LDAP administrator, for which a wrong data format is a serious trouble. But final user don't care about it. Instead of raising an error, I log a message. > Also, please use pcre (preg_match) instead of ereg in all Horde code > - it's much faster. If you could take a quick read through > horde/docs/CODING_STANDARDS that would be wonderful, for this or > future contributions, but I can fix this patch (whitespace mostly) as > it's small. Done. Thu, 20 Dec 2007 18:22:29 +0000 https://bugs.horde.org/ticket/6012#t40126 Committed to HEAD and FRAMEWORK_3 (soon to be Horde 3.2-RC2 and then Horde 3.2.0). Thanks! Thu, 20 Dec 2007 23:10:27 +0000 https://bugs.horde.org/ticket/6012#t40144