Ldap Error Code 67 Problem 6004
Search Username Password Remember Me? Register Lost Password? facebook google twitter rss Free Web Developer Tools Advanced Search Forum Programming Languages Java Help JNDI / LDAP error on modify user Thread: JNDI / LDAP error on modify user Share This Thread Tweet This + 1 this Post To Linkedin Subscribe to this Thread Subscribe to This Thread June 13th, 2007,09:57 PM #1 No Profile Picture scryptKiddy View Profile View Forum Posts Participant Devshed Newbie (0 - 499 posts) Join Date Sep 2005 Location Hawaii Posts 376 Rep Power 19 JNDI / LDAP error on modify user Well, seems I'm thread happy this week, google and forum searching got me nothing (or else I wouldn't post, hehe). Anyway, here goes: Scenario: I'm now able to create / modify users in AD via JNDI, yay! Except for one attribute (so far). Problem: When I try to modify the users "cn" using this: Code: ... //Create the initial directory context LdapContext ctx = new InitialLdapContext(env,null); Attributes myAttrs = new BasicAttributes(true); ModificationItem[] mods = new ModificationItem[5]; String Cn = "first1 m1 last1"; String userToModify = "'CN=" +Cn + ",OU=Test Users OU,DC=my,DC=company,DC=com'"; String newTitle = "newTitle2"; String newFirst = "newFirst2"; String newMiddle = "newMid2"; String newLast = "newLast2"; String newCn = "newFirst2"; //modify object mods[0] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("title",newTitle)); mods[1] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("givenName",newFirst)); mods[2] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("initials",newMiddle)); mods[3] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("sn",newLast)); mods[4] = new ModificationItem(DirContext.REPLACE_ATTRIBUTE, new BasicAttribute("cn",newCn)); ctx.modifyAttributes(userToModify, mods); ... It all works until I add the 5th mod ( mod[4] ) then I get this: Code:Problem searching directory: javax.naming.directory.SchemaViolationException: [LDAP: error code 67 - 000020B1: UpdErr: DSID-030F0A48, problem 6004 (CANT_ON_RDN), data 0 I guess it just can't be done? (yea right) So any Ideas? SK Faq Reply With Quote June 13th, 2007,10:24 PM #2 Yawmark View Profile View Forum Posts Visit Homepage Feelin' Groovy Devshed Supreme Being (6500+ posts) ༌
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://stackoverflow.com/questions/26850655/ldap-error-code-67-not-allowed-on-rdn the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each ldap error other. Join them; it only takes a minute: Sign up LDAP: error code 67 - Not Allowed On RDN up vote 0 down vote favorite I'm trying to import the following LDIF into Tivoli Directory Server .. dn: dc=root,dc=ibm,dc=com objectclass: domain objectclass: top dc: dc=root,dc=ibm,dc=com dn: cn=users,dc=root,dc=ibm,dc=com objectclass: domain objectclass: top dc: cn=users,dc=root,dc=ibm,dc=com I get this warning .. ldap error code According to the schema attribute CN is not allowed Followed by an error .. LDAP: error code 67 - Not Allowed On RDN I'm following some IBM documentation , so not sure where I'm going wrong? http://www-01.ibm.com/support/knowledgecenter/SSZLC2_7.0.0/com.ibm.commerce.admin.doc/tasks/tmswmmdirserver.htm ldap share|improve this question asked Nov 10 '14 at 18:42 bobbyrne01 1,38532145 This site is for programming questions. We are not general software/server tech support. –Marc B Nov 10 '14 at 18:43 add a comment| 2 Answers 2 active oldest votes up vote 0 down vote The objectclass domain does not allow the cn attribute according to your current schema (neither does top which is the mother of all objectlasses). Try dn: dc=users,dc=root,dc=ibm,dc=com instead because the dc attribute is available on domain entries. share|improve this answer answered Nov 10 '14 at 18:52 Stefan Gehrig 62.2k18106153 add a comment| up vote 0 down vote accepted Went with this .. dn: dc=root,dc=ibm,dc=com objectclass: domain objectclass: top dc: dc=root,dc=ibm,dc=com dn: cn=users,dc=root,dc=ibm,dc=com objectclass: container objectclass: top cn: cn=users,dc=root,dc=ibm,dc=com share|improve this answer answered Nov 11 '14 at 17:08 b