[MGNLLDAP-56] Incorrect change in lookup order breaks AD authentication Created: 10/Aug/11  Updated: 12/Aug/11  Resolved: 10/Aug/11

Status: Closed
Project: LDAP Connector
Component/s: None
Affects Version/s: 1.4.2
Fix Version/s: 1.4.3

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Magnolia International
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLLDAP-54 Allow extending login modules to iter... Closed
relation
is related to MGNLLDAP-53 UserID needs to be escaped when subst... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

As described in MGNLLDAP-53, the order in which the user dn and common name are retrieved in 1.4.2 has changed. This was caused by r43619 (for MGNLLDAP-54), and prevents from logging users in with their DN.


Generated at Mon Feb 12 02:21:08 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.