[MGNLLDAP-17] MS ActiveDirectory - allow configurable attribute for username authentication Created: 20/Jul/07  Updated: 27/Nov/13  Resolved: 21/Apr/11

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

Type: Improvement Priority: Major
Reporter: zam6ak Assignee: Jan Haderka
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLLDAP-35 Allow anonymous binding 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)
Date of First Response:

 Description   

Currently LDAP module uses DN (or distinguishedName) (for Active Directory) as a primary username while performing authentication.
On some installations CN can contain spaces (DN=John Doe) which Magnolia does not allow.
When authenticating agains MS Active Directory there should be an option to use sAMAccountName as username.



 Comments   
Comment by Sameer Charles [ 20/Jul/07 ]

We also need this module to work in SSO env. where we dont receive user credentials (password)
I will evaluate the possibilities..

Comment by Jan Haderka [ 21/Apr/11 ]

Fixed by changes made for MGNLLDAP-35. It is now possible to specify sAMAccountName in custom initial search filter

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