Meike Stone
2011-07-21 13:49:44 UTC
Hello,
I use JXplorer in a distributed LDAP Environment. The DIT is shared
among different LDAP servers (openLDAP) via referrals (RFC 3296).
Because of different Implementation of referral handling on client
side and network firewalls, we decided to use automatic referral
chasing on the server side.
OpenLDAP can do this via slapo-chain. This works very well.
But the JXplorer appends in the search request every time the Manage
DSA IT LDAPv3 control (2.16.840.1.113730.3.4.2). I traced this via
wireshark.
But in fact of this, openldap must send back the referral and does not
chase and the JXplorer does not follow the tree.
Is it possible, to disable this control? It would be great to do this
in the GUI, because sometime it is necessary to look for the referral
instead follow the tree.
Next Problem is, that I get the referral object, but the referral is
missing (empty field). I guess, thats because the referral is an
operational attribute and it must be requested explicit.
Client side chasing is not possible (option.ldap.referral), because
the servers how hold the subtrees are not reachable over network by
the clients.
Please help
Kindly regards
Meike
I use JXplorer in a distributed LDAP Environment. The DIT is shared
among different LDAP servers (openLDAP) via referrals (RFC 3296).
Because of different Implementation of referral handling on client
side and network firewalls, we decided to use automatic referral
chasing on the server side.
OpenLDAP can do this via slapo-chain. This works very well.
But the JXplorer appends in the search request every time the Manage
DSA IT LDAPv3 control (2.16.840.1.113730.3.4.2). I traced this via
wireshark.
But in fact of this, openldap must send back the referral and does not
chase and the JXplorer does not follow the tree.
Is it possible, to disable this control? It would be great to do this
in the GUI, because sometime it is necessary to look for the referral
instead follow the tree.
Next Problem is, that I get the referral object, but the referral is
missing (empty field). I guess, thats because the referral is an
operational attribute and it must be requested explicit.
Client side chasing is not possible (option.ldap.referral), because
the servers how hold the subtrees are not reachable over network by
the clients.
Please help
Kindly regards
Meike