Bug 821542
| Summary: | letters in object's cn get converted to lowercase when renaming object | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Noriko Hosoi <nhosoi> | ||||
| Component: | 389-ds-base | Assignee: | Rich Megginson <rmeggins> | ||||
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.3 | CC: | amsharma, ckannan, jgalipea, nkinder | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | 389-ds-base.1.2.10.2-12.el6 | Doc Type: | Bug Fix | ||||
| Doc Text: |
Cause: DN is internally normalized and the case information was dropped.
Consequence: Renaming a string in DN with the same string having different lower/uppercase dropped the case changes.
Fix: Fixed to keep the upper/lowercase info in the DN.
Result: Replacing only the cases in DN is now available.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-06-20 07:15:41 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Noriko Hosoi
2012-05-14 21:08:27 UTC
Created attachment 584480 [details]
git patch file (389-ds-base-1.2.10)
Back ported from master.
(Ported from commit 178fe6a74c793b3c6adc71f571bba40a6271325c)
1. ldapadd -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 << EOF dn: cn=AMITA,ou=people,dc=example,dc=com cn: AMITA sn: ams givenname: ams objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetOrgPerson uid: ams mail: ams userpassword: amsamsams EOF 2. [root@dhcp201-194 ~]# ldapsearch -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 -b "cn=AMITA,ou=people,dc=example,dc=com" # extended LDIF # # LDAPv3 # base <cn=AMITA,ou=people,dc=example,dc=com> with scope subtree # filter: (objectclass=*) # requesting: ALL # # AMITA, People, example.com dn: cn=AMITA,ou=People,dc=example,dc=com cn: AMITA sn: ams givenName: ams objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson uid: ams mail: ams userPassword:: e1NTSEF9R21HTTRHNVRWYWxSbjI3MFp5VkkxSlBxNE5CMzUvOXMrQ0V5MUE9PQ= = # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 3. [root@dhcp201-194 export]# cat rdn.txt cn=AMITA,ou=people,dc=example,dc=com cn=SHARMA 4. ldapmodrdn -x -w Secret123 -D "cn=directory manager" -r -v -f rdn.txt [root@dhcp201-194 export]# ldapmodrdn -x -w Secret123 -D "cn=directory manager" -r -v -f rdn.txt ldap_initialize( <DEFAULT> ) Renaming "cn=AMITA,ou=people,dc=example,dc=com" new rdn="cn=SHARMA" (delete old rdn) Rename Result: Success (0) 5. ldapsearch -x -h localhost -p 389 -D "cn=Directory Manager" -w Secret123 -b "ou=people,dc=example,dc=com" # SHARMA, People, example.com dn: cn=SHARMA,ou=People,dc=example,dc=com sn: ams givenName: ams objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson uid: ams mail: ams userPassword:: e1NTSEF9R21HTTRHNVRWYWxSbjI3MFp5VkkxSlBxNE5CMzUvOXMrQ0V5MUE9PQ= = cn: SHARMA HENCE VERIFIED.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Cause: DN is internally normalized and the case information was dropped.
Consequence: Renaming a string in DN with the same string having different lower/uppercase dropped the case changes.
Fix: Fixed to keep the upper/lowercase info in the DN.
Result: Replacing only the cases in DN is now available.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-0813.html |