Ldap Error 34 Invalid Dn Syntax
Contents |
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
English » 2. Using Liferay » General Recent Posts Statistics RSS (Opens New Window) Answer (Unmark) Mark as an ldap error code 34 - invalid dn jxplorer Answer Threads [ Previous | Next ] LDAP Error 34 ldap error code 34 data 8349 - Where is the problem? Robert Mueller March 6, 2012 3:49 AM RE: LDAP ldap error code 34 invalid dn apache directory studio Error 34 - Where is the problem? ahmad abuoun March 11, 2012 1:12 AM RE: LDAP Error 34 - Where is the problem? Robert https://groups.google.com/d/topic/macromedia.coldfusion.security/Rq7xx15OeBs Mueller March 14, 2012 1:57 AM RE: LDAP Error 34 - Where is the problem? Hitoshi Ozawa March 14, 2012 4:36 AM RE: LDAP Error 34 - Where is the problem? ahmad abuoun March 14, 2012 7:27 AM RE: LDAP Error 34 - Where is the problem? https://web.liferay.com/community/forums/-/message_boards/message/12851021 Robert Mueller March 15, 2012 12:48 AM LDAP Error 34 - Where is the problem? March 6, 2012 3:49 AM Answer Robert Mueller Rank: New Member Posts: 5 Join Date: September 21, 2011 Recent Posts Hi there.For a while I'm getting a LDAP-Error 34 when I try to login.If an user tries to login the first time, he gets the message, that his logindata is wrong.After trying a second time he can login. All attributes are imported. Now he can login like "normal".But in the logfile I get an exception, if a user logs in:111:31:47,158 ERROR [LDAPAuth:318] Problem accessing LDAP server2javax.naming.InvalidNameException: ou=T-EST,dc=TEST: [LDAP: error code 34 - Invalid DN Syntax]; remaining name 'ou=T-EST,dc=TEST'3 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2943)4 at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2758)5 at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1812)6 at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1735)7 at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:368)8 at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:338)9 at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:32
Favorite Rating: LDAP Error 34: Invalid dn syntax. (Last modified: 27Feb2006) This document (10067272) is provided subject to the disclaimer at the end http://www.novell.com/support/kb/doc.php?id=10067272 of this document. fact GroupWise Support Pack 2 Novell GroupWise 6 GroupWise LDAP Authentication Authenticating to a different NDS tree for LDAP symptom LDAP Error 34: Invalid dn syntax. cause GroupWise was building an invalid distinguished name to be passed to LDAP for the other tree fix The reason that the dn is reported as being invalid is due to the manner in ldap error which the GroupWise Post Office Agent builds the distinguished name that is passed to the LDAP server. GroupWise takes the typeful distinguished NDS name of the user and converts it to an LDAP typeful distinguished name. Thus, cn=user.ou=org.o=novell.t=novell_tree becomes cn=user, ou=org, o=novell.tree=novell_tree. Since the authentication is being done to an external tree, the tree name will obviously not match and the authentication will ldap error code fail.There are two possible solutions to this problem the first is to populate the LDAP Authnentication field on the properties of the user, GroupWise Account tab. This should be populated with the LDAP distinguished name without the tree name:cn=user, ou=org, o=novellThis will have to be done for each user.The other solution requires GroupWise 6 Support Pack2 or later. If the LDAPX.DLL for Windows or the LDAPX.NLM for NetWare is renamed in the directory where the POA executables are found, then the POA will use the NDS Email Address Attribute to authenticate. This attribute is populated automatically by GroupWise if Internet Addressing is enabled. The POA then passes the mail attribute as well as the password supplied by the user logging in to authenticate against LDAP. The other tree must have an exact match in the email address attribute for the authentication to be successful. There are three Groupwise LDAP modules: ldapx.nlmldapssl.nlmldapsdk.nlmThe modify date on the LDAP modules shipped with Groupwise 6.5 Support Pack 2 is 1/13/2003. The modify Date onthe LDAP modules shipped with Netware 6.5 Support Pack 2 is 11/14/2003.One customer reported that the problem wit