Hi,
I'm not sure if it is that easy to do inside the API. E.g. the
referenced server may use different bind DN, password, even other
connection parameters. I have recently implemented it in my ConnId
connector. And it required to use quite a lot of "application"
configuration magic to handle the referral connections at least a tiny
bit correctly.
The referral handling is obviously doable even now if the client is
implemented well. E.g. like this (lines 109-119):
https://github.com/Evolveum/connector-ldap/blob/master/src/main/java/com/evolveum/polygon/connector/ldap/search/DefaultSearchStrategy.java
Referral handling is not that hard. Connection management seems to be
harder:
https://github.com/Evolveum/connector-ldap/blob/master/src/main/java/com/evolveum/polygon/connector/ldap/ConnectionManager.java
So, I believe that we can do something simple in the API to be able to
follow referrals when all the connection parameters (except for
hostname/port) are the same. But even in that case it will include
management of several connections to several servers. Any slightly
complex case would be perhaps too hard to implement in the API anyway.
And as there is usually some application-specific logic involved it is
perhaps not the best candidate to invest the development time.
--
Radovan Semancik
Software Architect
evolveum.com
On 03/04/2016 12:34 AM, Emmanuel Lécharny wrote:
Le 03/03/16 22:52, SG a écrit :
I' am using LDAP API 1.0.0-M33 and want the api to follow referrals
automatically (for lookup and search).
Ist this supported and if yes where can i set that referrals should be followed.
Sadly, no, it's not yet supported.
It's one of the latest thing we have to add to the API to get a 1.0-RC
out...
