Hi, I started with LDAP just recently and I successfully built and implemented a custom schema. However there is one problem. I am required to add "userPasswordAtt" attribute to my custom schema which is similar to "userPassword" attribute in "inetOrgPerson" schema.
This is what I tried so far:
attributetype ( 1.28.7.2011.13.1 NAME 'userPasswordAtt' EQUALITY octetStringMatch SYNTAX 1.3.6.1.4.1.1466.115.121.1.40)
It is basically a copy/paste of "userPassword" attribute.
objectclass ( 1.28.7.2011.1.1 NAME 'eOskrbaPerson' DESC 'e-oskrba participant' SUP top STRUCTURAL MUST ( bidAtt $ uidAtt $ cnPatient $ userPasswordAtt ) MAY ( patientCoopFlagAtt $ patientsDoctorAtt $ eMailAtt $ dateOfBirthAtt $ sexAtt $ healthcareInstitutionAtt $ memberAtt $ mobilePhoneAtt $ experimentalGroupAtt ) )
But with this attribute I can not log in to phpLDAPadmin for example. It also doesn't cover password with dots on creation as it does with "userPassword". As far as I know "userPassword" is never defined as password in any schema, I am suspecting that it has to be somehow hardcoded (I also checked inheritance which goes all the way from core.schema).
So far I also tried to avoid inheriting attributes from defined schemas.
How can I use my custom attribute in the same way as "inetOrgPerson->userPassword"?
Some pointers for future research would be greatly appreciated.
Regards, Janez Barbic
Janez Barbič wrote:
I started with LDAP just recently and I successfully built and implemented a custom schema. However there is one problem. I am required to add "userPasswordAtt" attribute to my custom schema which is similar to "userPassword" attribute in "inetOrgPerson" schema.
What exactly do you want to achieve?
But with this attribute I can not log in to phpLDAPadmin for example.
Yes, slapd does not know that it should use your custom password attribute. AFAIK you can't use a custom attribute for password-checking during a bind request. You could implement something like this on your client-side custom code.
As far as I know "userPassword" is never defined as password in any schema, I am suspecting that it has to be somehow hardcoded
Some attribute types are hard-coded in schema_prep.c since they are needed during boot-strapping a server with dynamic configuration.
Ciao, Michael.
openldap-technical@openldap.org