[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
custom password attribute
- To: openldap-technical@openldap.org
- Subject: custom password attribute
- From: Janez BarbiÄ <jhnsmth64@gmail.com>
- Date: Sat, 6 Aug 2011 08:09:19 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=CNGmW3lyrtfSCRukaUNfJ22mCxYXHsE7gQ4mRkj/sUg=; b=Y5qKdqH3hhZhaZcYUVNfYRV75ZQ3PJinPAIs9GVr+K5/UTRzthctAQIvCcPjvmkAIg OQrxGRQwk3/d01/tgyuzpc2+AQgRKpl16QTGP1tBYHtsGznfeDGue3MYXuY05J0FYQjL ZVtDr55aJry3Oegcz8i7iylN+prCpoC2VRwL4=
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