Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: 19
Affects Version/s: 8u261, 11.0.8-oracle, 17
Component/s: core-libs
Labels:

Subcomponent:
javax.naming
Resolved In Build:
b23
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8324814	17.0.12-oracle	Ravi Reddy	P4	Resolved	Fixed	b01
JDK-8293664	17.0.6	Paul Hohensee	P4	Resolved	Fixed	b01
JDK-8324813	11.0.24-oracle	Ravi Reddy	P4	Resolved	Fixed	b01
JDK-8293663	11.0.18	Paul Hohensee	P4	Resolved	Fixed	b01
JDK-8302737	openjdk8u372	Alexey Bakhtin	P4	Resolved	Fixed	b04
JDK-8324815	8-pool	Ravi Reddy	P4	Open	Unresolved

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.

backported by

JDK-8324815 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Open

JDK-8293663 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Resolved

JDK-8293664 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Resolved

JDK-8302737 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Resolved

JDK-8324813 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Resolved

JDK-8324814 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Resolved

csr for

JDK-8276959 Retrying a failed authentication on multiple LDAP servers can lead to users blocked

Closed

relates to

JDK-8160768 Add capability to custom resolve host/domain names within the default JNDI LDAP provider

Resolved

links to

Commit openjdk/jdk8u-dev/b51619d2

Commit openjdk/jdk11u-dev/0dc10359

Commit openjdk/jdk17u-dev/f0acd72f

Commit openjdk/jdk/3be394e1

Review openjdk/jdk8u-dev/117

Review openjdk/jdk8u-dev/268

Review openjdk/jdk11u-dev/1351

Review openjdk/jdk17u-dev/654

Review openjdk/jdk/6043

(1 backported by, 1 csr for, 1 relates to, 9 links to)

Assignee:: Martin Balao Alonso

Reporter:: Martin Balao Alonso

Votes:: 0 Vote for this issue

Watchers:: 10 Start watching this issue

Created:: 2021-10-19 12:52

Updated:: 2024-02-27 02:06

Resolved:: 2022-05-12 09:21

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates