Hello, I would like to know if it is possible to have an aliasedobjectname reference an object that is defined in a different database as a different suffix on the same server. I have deref set to always but it doesn't seem to be following the alias as long as it is not on its own suffix. Below is an example of what I am trying to do.
suffix1: dc=example,dc=com dn: cn=entry,dc=example,dc=com ...
suffix2: dc=example,dc=net dn: cn=entry2,dc=example,dc=net objectClass: alias objectClass: extensibleObject aliasedobjectname: cn=entry,dc=example,dc=com
So I guess what I need is subordinate/superior database gluing. Except in my case I do not want subordinates and a superior, I just want the two databases to be able to talk to one another, specifically via aliasedobject calls. Any suggestions?
On Fri, Aug 12, 2011 at 9:46 PM, Tyler Gates tgates81@gmail.com wrote:
Hello, I would like to know if it is possible to have an aliasedobjectname reference an object that is defined in a different database as a different suffix on the same server. I have deref set to always but it doesn't seem to be following the alias as long as it is not on its own suffix. Below is an example of what I am trying to do.
suffix1: dc=example,dc=com dn: cn=entry,dc=example,dc=com ...
suffix2: dc=example,dc=net dn: cn=entry2,dc=example,dc=net objectClass: alias objectClass: extensibleObject aliasedobjectname: cn=entry,dc=example,dc=com
Tyler Gates wrote:
Hello, I would like to know if it is possible to have an aliasedobjectname reference an object that is defined in a different database as a different suffix on the same server.
No. Use a referral.
Thanks. I tried that before but didn't realize the client had to be told to follow the referral so I gave up on it.
On 08/15/2011 05:35 PM, Howard Chu wrote:
Tyler Gates wrote:
Hello, I would like to know if it is possible to have an aliasedobjectname reference an object that is defined in a different database as a different suffix on the same server.
No. Use a referral.
openldap-technical@openldap.org