-
Bug
-
Resolution: Fixed
-
Medium
-
3.7.1
-
3.07
-
7
-
JIRA LDAP-based password checking fails if the DN contains a slash:
28-Aug-2007 13:22:55 com.opensymphony.user.provider.ldap.LDAPCredentialsProvider authenticateSEVERE: Initial connect and search successful, but second phase connection to LDAP as '"CN=Tester,OU=Central/East Europe,OU=User Accounts,OU=London,dc=sample,dc=com' failed.javax.naming.InvalidNameException: "CN=Tester,OU=Central/East Europe,OU=User Accounts,OU=London,dc=sample,dc=com: close quote appears before end of component at javax.naming.NameImpl.extractComp(NameImpl.java:129) at javax.naming.NameImpl.<init>(NameImpl.java:267) at javax.naming.CompositeName.<init>(CompositeName.java:214) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:321)
- is blocked by
-
CWD-2042 Forward slashes not escaped correctly in DNs etc.
- Closed
- is related to
-
CONFSERVER-10091 OSUser LDAP authentication fails when there is a slash ("/") in DN
- Closed
-
CWD-183 Problems with LDAP group or user names that contain / or \.
- Closed
-
CWD-2898 Use LdapName consistently when manipulating DNs
- Closed
- 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-13005 LDAP authentication against Active Directory fails if there are escaped double quotes in the user's CN
- Closed
-
JRASERVER-21579 LDAP authentication fail when"\" exist in DN
- Closed
- is incorporated by
-
JRADEV-11821 Loading...