Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: Medium
Fix Version/s: 2.5.1
Affects Version/s: None
Component/s: Directory - LDAP
Labels:
None

Some of the Crowd code currently uses CompositeName when constructing DNs. This class parses according to JNDI rules, so forward slashes need to be escaped correctly (~~CWD-2875~~, etc.) to avoid splitting before passing to LDAP.

Instead, we should use javax.naming.ldap.LdapName consistently. This involves changing one interface (com.atlassian.crowd.directory.ldap.name.Converter) in the internal API.

relates to

FE-3184 Cannot authenticate LDAP Usernames with '/' in CN

Closed

JRASERVER-13325 LDAP against AD will not authenticate when DN includes a ','.

Closed

JRASERVER-13470 LDAP authentication fail when slash "/" exist in DN

Closed

CONFCLOUD-26394 LDAP authentication fails when DN contains slash, comma or double quotes

Closed

CONFSERVER-26394 LDAP authentication fails when DN contains slash, comma or double quotes

Closed

JRACLOUD-13005 LDAP authentication against Active Directory fails if there are escaped double quotes in the user's CN

Closed

JRASERVER-13005 LDAP authentication against Active Directory fails if there are escaped double quotes in the user's CN

Closed

supersedes

CWD-1152 Issues exist with DNs or Group Names that contain special characters

Closed

CWD-2042 Forward slashes not escaped correctly in DNs etc.

Closed

(2 relates to, 2 supersedes)

Assignee:: joe
Reporter:: joe
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: 14/Aug/2012 3:49 AM
Updated:: 15/Aug/2019 7:06 AM
Resolved:: 27/Aug/2012 2:31 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates