[KARAF-3711] LDAP login module doesn't handle case where CN, OU, DC case doesn't match

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.4, 4.0.0, 2.4.3
• Assignee: Jonathan Anstey
• Reporter: Jonathan Anstey
• Created: 28/Apr/15 17:00
• Updated: 28/Apr/15 17:29
• Resolved: 28/Apr/15 17:29

Description

Had a user whose AD server was returning userDN of "CN=Foo Bar,OU=groups,DC=example,DC=com" but "ou=people,dc=example,dc=com" was specified for user.base.dn. The current code would fail to bind the user because of the case mismatch. This is perfectly legal in LDAP so I'm gonna fix that up...