#405 referint modrdn not working if case is different
Closed: wontfix None Opened 11 years ago by rmeggins.

Steps:

  • setup directory server with DIT

dc=example,dc=com
ou=People,dc=example,dc=com # NOTE uppercase People
ou=Groups,dc=example,dc=com

  • Enable referint
  • Add group entry cn=allusers,ou=Groups,dc=example,dc=com like this:

    dn: cn=allusers,ou=Groups,dc=example,dc=com
    objectClass: top
    objectClass: groupofNames
    cn: allusers
    description: default group for users

  • Add a user entry uid=testuser1,ou=People,dc=example,dc=com

  • Add member: uid=testuser1,ou=people,dc=example,dc=com to cn=allusers group
  • modrdn uid=testuser1

ldapmodify ... <<EOF
changetype: modrdn
newrdn: uid=testuser1changed
deleteoldrdn: 1
EOF

  • search cn=allusers - it still lists the old dn

member: uid=testuser1,ou=people,dc=example,dc=com

Looking at the referint code, _update_one_per_mod() and _update_all_per_mod() are doing a PL_strstr - comparing a case normalized value against an un-case normalized value (that is, normalized but not case normalized).


branch 389-ds-base-1.2.11
commit changeset:69ce800/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Mon Jul 9 15:24:25 2012 -0600

branch master
commit changeset:6ba24eb/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Mon Jul 9 15:24:25 2012 -0600

branch 389-ds-base-1.2.10
commit db69b14
Author: Rich Megginson rmeggins@redhat.com
Date: Mon Jul 9 15:24:25 2012 -0600

fixed in 389-ds-base-1.2.10.13

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.2.11.8

7 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/405

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata