Project

General

Profile

Bug #309

metacat does not follow LDAP referrals

Added by Matt Jones almost 18 years ago. Updated over 17 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
metacat
Target version:
Start date:
10/25/2001
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
309

Description

Metacat can't authenticate against the LTER ldap db because it doesn't need to
follow referrals properly. It was never implemented this way. Need to modify
the AuthLdap class to do so. This can be done by following the examples for
JNDI at ther following url:

http://java.sun.com/products/jndi/tutorial/ldap/referral/follow.html

History

#1 Updated by Matt Jones almost 18 years ago

Have a potential fix in place on the 'jones' context testing environment. Need
someone (David?) with an LTER account to test if login now works using referrals.

#2 Updated by Chad Berkley almost 18 years ago

I'm pretty sure the referrals are working correctly, however now, when a user logs in it takes on the order of 10-15 seconds for the login action to finish. I have traced this to the method javax.naming.NamingEnumeration.hasMore(). This method is called several times in the method edu.ucsb.nceas.metacat.AuthLdap.getIdentifyingName(). Everytime this method is executed there is a 2-5 second delay in the execution of metacat.

#3 Updated by Chad Berkley almost 18 years ago

referrals are now working.

#4 Updated by Chad Berkley almost 18 years ago

referrals are now working

#5 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 309

Also available in: Atom PDF