There is no need to define a dateOfBirth
attribute. The auxiliary objectClass naturalPerson
- described in RFC2985 - already allows this attribute using generalizedTimeSyntax
. Add the naturalPerson
objectClass to your entry, then add a dateOfBirth
attribute that conforms to generalizedTimeSyntax
.
dn: cn=myPerson,dc=example,dc=com
objectClass: top
objectClass: inetOrgPerson
objectClass: naturalPerson
dateOfBirth: 20121115121912.810Z
and so forth.
Update: example objectClass definition from RC2985.
dn: cn=schema
objectClass: top
objectClass: ldapSubentry
objectClass: subSchema
objectClasses: ( 1.2.840.113549.1.9.24.2 NAME 'naturalPerson'
SUP top
AUXILIARY
MAY ( emailAddress $
unstructuredName $
unstructuredAddress $
dateOfBirth $
placeOfBirth $
gender $
countryOfCitizenship $
countryOfResidence $
pseudonym $
serialNumber )
X-ORIGIN 'RFC 2985' )