Bug 90145 - ntlm auth sheme is missing
Summary: ntlm auth sheme is missing
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: squid
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Martin Stransky
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-05-03 13:10 UTC by Grégory BENOIST
Modified: 2007-04-18 16:53 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-07-01 12:42:19 UTC
Embargoed:


Attachments (Terms of Use)

Description Grégory BENOIST 2003-05-03 13:10:26 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
When trying to use NTLM authentication sheme, squid reports:
 Parsing Config File: Unknown authentication scheme 'ntlm'.


Version-Release number of selected component (if applicable):
squid-2.5.STABLE1-2

How reproducible:
Always

Steps to Reproduce:
1.enable auth_param ntlm with program /usr/lib/ntlm_auth
2.restart squid
3.observe the output
    

Actual Results:   Parsing Config File: Unknown authentication scheme 'ntlm'.

Expected Results:  work like a charm :)

Additional info:

added a "--enable-auth \" line in the squid.specs file and recompiled the RPM 
worked for me.

Comment 1 Economou, Matthew 2003-05-15 09:09:04 UTC
What's really strange is that the NTLM authentication helper modules were built 
for Squid, so one is lead to believe that NTLM authentication will work.  This 
is not the case.  Squid must be built with the '--enable-auth="basic,ntlm"' 
argument to configure in addition to the helper module flags in order for NTLM 
support to be activated.

To fix this problem, the Red Hat release engineer need only add the above 
configure flag and rebuild the package.

Comment 2 Reuben Farrelly 2004-01-29 11:34:55 UTC
This feature was added in the latest squid RPM in Rawhide, in June 
2003.  I think this bug should be closed as 'resolved' now.. 


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