David Chadwick wrote:
Hi Howard
Howard Chu wrote:Looks like I forgot about this. Just to note: I've added pwdStartDate and pwdEndDate to the LDAP ppolicy draft, and suggested that setting pwdStartDate to a value greater than pwdEndDate can be used for the same effect as a generic "disabled" flag.good idea. We will change the name of our pwdCreationTime to pwStartTime and allow it to be in the future and set by the administrator. We should then have alignment on this As an aside, dont you think we should try to align the names (and OIDs) of all our attributes when they are semantically the same. For example, we use Time rather than Date since we use GeneralisedTime as the syntax of many of our attributes.
Yes, that would make the most sense. I didn't want to tackle that since I wasn't sure how much flexibility you have here. Given that there are already a lot of deployments of the LDAP revision 9 draft, I don't really want to go back and change the definitions from that revision. But certainly for the stuff I've added in revision 10 I'm open to more intuitive choices.
You can find the latest edit in the OpenLDAP CVS http://www.openldap.org/devel/cvsweb.cgi/doc/draftsIf you get me a copy of your latest edit I can generate a list of attributes that we can align.
-- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/ ----- www.x500standard.com: The central source for information on the X.500 Directory Standard.
