Bug 2053284

Summary:	Retrying a failed authentication on multiple LDAP servers can lead to users blocked [rhel-8, openjdk-11]
Product:	Red Hat Enterprise Linux 8	Reporter:	Andrew John Hughes <ahughes>
Component:	java-11-openjdk	Assignee:	Martin Balao <mbalao>
Status:	CLOSED ERRATA	QA Contact:	OpenJDK QA <java-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	jandrlik, pmikova
Target Milestone:	rc	Keywords:	Triaged, ZStream
Target Release:	---	Flags:	ahughes: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	java-11-openjdk-11.0.14.1.1-5.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	2055341 2055342 2055343 2055344 (view as bug list)		Environment:
Last Closed:	2022-05-10 13:40:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2055341, 2055342, 2055343, 2055344

Description Andrew John Hughes 2022-02-10 20:50:38 UTC

This bug was initially created as a copy of Bug #2053256

I am copying this bug because: 

JDK-8160768 also in 11u.

After JDK-8160768, the behavior upon a failed LDAP authentication changed: instead of aborting the operation with an AuthenticationException exception, all available LDAP servers are tried with the same credentials. Note that the credentials might be wrong because of an error when the user entered them (i.e.: a typo). If this is the case, the user may be blocked on all LDAP servers after a single operation because of exceeding the maximum number of authentication failures. In my view, an authentication error means that the LDAP server is alive and there is no need to iterate to a different endpoint.

Comment 11 errata-xmlrpc 2022-05-10 13:40:26 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (java-11-openjdk bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:1799