On 16/12/03 8:39 am, David Syzdek <[EMAIL PROTECTED]> wrote:
Are there plans to expand add(), delete(), moddn(), and modify() to follow referrals?
Not especially, but if a clean design was suggested then I'm sure it would
be considered.
I am currently following referrals by checking for ($ldap->code == 10)
and making a second LDAP connection. Being able to pass new() an
additional parameter that instructs Net::LDAP to follow referrals would
make developing scripts that point to consumers and have to follow
referrals to the suppliers a lot easier.
How would you handle authenticating to the other servers? Net::LDAP
deliberately does not cache authentication credentials, so it wouldn't be
completely trivial - you almost certainly wouldn't want to offer credentials
valid for server A to server B for example. What if there are multiple
referrals which could be followed - which choice should be taken?
I apologize in advance if this has already been discussed or covered in
documentation I missed.
It comes up occasionally...
It came up recently. My suggestion is that the user should be able to register a callback with Net::LDAP that Net::LDAP will call when it needs a connection to a different server. It would pass the URL details from the referral and expect a Net::LDAP object back, which it would then send the request to.
Graham.
