Bug 35432 – Squid basic auth failed after user changed password in client

Bug 35432 - Squid basic auth failed after user changed password in client


Summary:	Squid basic auth failed after user changed password in client

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Squid
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 3.x
Assigned To:	Squid maintainers
QA Contact:

URL:
Keywords:

Depends on:	34206
Blocks:
	Show dependency tree / graph

Reported:	2014-07-22 12:13 CEST by Florian Best
Modified:	2017-08-08 07:11 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Florian Best

2014-07-22 12:13:25 CEST

The same bug exists also for HTTP basic authentication.

+++ This bug was initially created as a clone of Bug #34206 +++

If a user change his password (in a windows session), the proxy always shows the auth window, but the new password mismatch. The old password is accepted.
I think the cache in /usr/lib/squid3/squid_ldap_ntlm_auth line 305 is the problem. A windows logout/login doesn't solve the problem, only a restart of squid resolve it.

# auth ntlm in squid.conf
auth_param ntlm program /usr/lib/squid3/squid_ldap_ntlm_auth
auth_param ntlm children 50
auth_param ntlm keep_alive off

Comment 1 Stefan Gohmann

2017-06-16 20:39:48 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 2 Stefan Gohmann

2017-08-08 07:11:44 CEST

This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.