[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Storing references...
Ya, groupOfUniqueNames should solve this issue. But my original problem was
different. Having an attribute to store the reference. Actually I've an
entry which has attribute "cn" which store lot of values as shown below :
dn:
cn=Permissions,cn=CorrespondenceRBA,cn=CCU,ou=Roles,ou=ABS,ou=Application,o=
Agilisys
ou: Application
ou: ABS
ou: Roles
cn: CCU
cn: HERE I WANT TO STORE THE REFERENCE...... LIKE
cn=Reports,ou=Components,ou=ABS,ou=Application,o=Agilisys
cn: Permissions
member: cn=Read,ou=Permissions,ou=ABS,ou=Application,o=Agilisys
objectclass: groupOfNames
Now as I have multiple values for attrubute 'cn' diffucult to get actual
reference to the object which I've shown as
"cn=Reports,ou=Components,ou=ABS,ou=Application,o=Agilisys"
Is there any other attribute which I can use instead of cn for
storing this reference ?????
Thanks,
Mahesh
-----Original Message-----
From: Adam Williams [mailto:awilliam@whitemice.org]
Sent: Monday, April 01, 2002 5:46 PM
To: Mahesh Patil
Cc: 'openldap-software@OpenLDAP.org'
Subject: RE: Storing references...
>No, not alias object. As far as I understood from alias object, if I use
>alias instead of complete DN and if I delete this entry which has reference
>to original object then the original object also gets deleted !!!
>I have a structure wherein I have all users defined under "Employee"
>node. When I declare different modules, I specify all users having access
to
>that perticular module. If I use alias here and lateron try to remove any
>user from the module then it'll delete that user from original list under
>"Employees" !!!
>Please, Correct me If I'm wrong !!
Ok, I understand better now. Why not use a groupOfUniqueNames object
for each module? This is pretty much exactly what they are for, or do
you need to store additional information per user for each module they
have access to?
I don't know if the alias manages auto-deletion of the referred object,
I'd be rather surprised if it does. Anyone?