Project

General

Profile

Bug #2764

LDAP client should handle referral failure correctly

Added by Jing Tao almost 13 years ago. Updated over 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
metacat
Target version:
Start date:
02/08/2007
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2764

Description

Today, a knb website user reported that she could not register an ldap account through the knb web site. The result turned out is that a new referral, which is not up, was added to the ldap server. The failure of referral cause ldapweb.cgi failed. It seems that Morpho couldn't get ldap tree correctly either.

The reason of the failure is the ldap client couldn't handle the situation that referral ldap is down.

History

#1 Updated by Jing Tao over 12 years ago

The reason is the ldapweb.cgi called "die" command if a ldap server is down and obviously appache is not good at the die command. Now we changed the rules. If main ldap server is down, a error page will return to the user. If referral server is down, it will be ignored silently.

#2 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2764

Also available in: Atom PDF