From: Christoph N. <en...@ap...> - 2001-11-28 22:22:14
|
It seems that if the user opts to have Net::LDAP remember the credentials it is no different then if the user's program stores the credentials. I think the facility for automatically chasing referrals should exist withing Net::LDAP. The user must opt to use it. The chasing process should also be very well defined in the docs so that a user can decide when they may need to implement it themselves. Simply because the code will not cover every chasing scenario, doesn't mean it won't be useful for many senarios. Why should everyone have to write and test their own code for chasing referrals when a well planned approach within Net::LDAP would sufice for many people. After all, it would be optional. - Christoph On Wed, 28 Nov 2001, Clif Harden wrote: > > > > On Wed, Nov 28, 2001 at 03:00:31PM +0000, John Berthels wrote: > > > > Basically my thought was that the user would have to tell Net::LDAP > > > > that they want to chase referrals by registering a sub which, given an > > > > LDAP URL, would create the connection and do the auth. > > > > > > > > I have not thought much beyond that, so if anyone want to bounce a few > > > > ideas, go ahead > > > > > > I think the ability to pass in a sub to do the bind is a good idea. > > > > Not just the bind, the connection too. This would allow the application > > to do cacheing of the connections if it whished. I do not expect > > Net::LDAP to cache connections from chasing referrals. > > > > > Presumably one concern is that chasing a referral attempts a bind to > > > another server, which involves presenting credentials, sometimes a > > > cleartext password. > > > > Right, but with this approach that is completely under the control of the application > > > > I would like to see everything stay with application/user supplied > subroutine. This puts the application/user in control of everything. > Odds are that any of us that chase referrals already have this > methodology implemented. > > Clif |