Bug 44986 - LDAP user authentication fails
LDAP user authentication fails
Product: Red Hat Powertools
Classification: Retired
Component: bugzilla (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: bero
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-06-19 09:54 EDT by Toralf
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-17 10:55:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Toralf 2001-06-19 09:54:18 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.77 [en] (X11; U; Linux 2.4.5-0.2.9 i686)

Description of problem:

How reproducible:

Steps to Reproduce:
1. Set useLDAP to "on" and insert correct LDAPserver/LDAPbaseDN
in editparams.cgi
2. Login via query.cgi?GoAheadAndLogIn=1

Actual Results:  Can't locate object method "new" via package
"Mozilla::LDAP::Conn" at CGI.pl line 719.

Expected Results:  User logged in and allowed to create/update bug reports.

Additional info:

Clearly related to this [from CGI.pl]:

# commented out the following snippet of code. this tosses errors into the
# CGI if you are perl 5.6, and doesn't if you have perl 5.003.
# We want to check for the existence of the LDAP modules here.
# eval "use Mozilla::LDAP::Conn";
# my $have_ldap = $@ ? 0 : 1;

Also note that bugzilla was updated via link on


before testing.
Comment 1 Tim Powers 2001-06-27 16:56:33 EDT
You may want to try the bugzilla here now and let me know if it works or not:


Comment 2 Toralf 2001-08-08 03:59:42 EDT
I'm sorry I haven't been able to test this earlier, I've just been very busy,
and also needed to tweak the LDAP database a bit before I could use it without
having to regenerate all user profiles in Bugzilla.

Anyhow, nothing seems to have changed (except, of course, that other problems I
reported have been resolved). I still get the same error message.
Comment 3 Bernhard Rosenkraenzer 2002-01-18 12:12:21 EST
This should be fixed in the 2.14.1 erratum released recently.

Note You need to log in before you can comment on or make changes to this bug.