Bug 150907

Summary: LDAP Authentication fails with an assertion error.
Product: Red Hat Enterprise Linux 4 Reporter: Jon Orris <jorris>
Component: squidAssignee: Jay Fenlason <fenlason>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: david.smith, garry.optland, jfeeney
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHSA-2005-415 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-14 19:43:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jon Orris 2005-03-11 21:19:05 UTC 
Description of problem:
The LDAP authentication module in squid fails with an assertion error. 

For example, given a sample LDAP server with user uid 'foo' pwd 'bar', do:

/usr/lib/squid/squid_ldap_auth -b "ou=People,dc=example,dc=com" -h
some.ldap.server.com -f "uid=%s"
foo bar
squid_ldap_auth: ../../../libraries/libldap/search.c:189: ldap_search: Assertion
`ld != ((void *)0)' failed.
Aborted

On RHEL3, this gives:
/usr/lib/squid/squid_ldap_auth -b "ou=People,dc=example,dc=com" -h
some.ldap.server.com -f "uid=%s"
foo bar
OK

The effect is that LDAP auth on rhel4 doens't work at all, whereas it is working
fine on RHEL3-U4.


Will attach sample squid.conf.
Comment 1 David Smith 2005-04-07 07:32:28 UTC 
I don't think it is necessary to attach a squid.conf as the problem is
independent of the squid setup - the squid_ldap_auth app fails
standalone and as a squid helper.

This looks the same as bug 141938
Comment 2 Garry Optland 2005-05-06 22:11:28 UTC 
squid_ldap_auth from FC3 (version squid-2.5.STABLE9-1.FC3.4) has this bug fixed.
Comment 3 Josh Bressers 2005-06-14 19:43:07 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHSA-2005-415.html