Bug 1048980

Summary: 7-bit check plugin not checking MODRDN operation
Product: Red Hat Enterprise Linux 7 Reporter: Jenny Severance <jgalipea>
Component: 389-ds-baseAssignee: Rich Megginson <rmeggins>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: medium Docs Contact:
Priority: low    
Version: 7.0CC: jrusnack, nhosoi, vashirov
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.3.1-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1034265 Environment:
Last Closed: 2015-03-05 09:33:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1034265    
Bug Blocks:    

Comment 2 Viktor Ashirov 2014-12-26 01:40:04 UTC
$ rpm -qa | grep 389
389-ds-base-debuginfo-1.3.3.1-10.el7.x86_64
389-ds-base-1.3.3.1-10.el7.x86_64
389-ds-base-libs-1.3.3.1-10.el7.x86_64

dn: cn=7-bit check,cn=plugins,cn=config
nsslapd-pluginEnabled: on
nsslapd-pluginarg0: uid

$ ldapmodify -D 'cn=Directory Manager' -w Secret123 -H ldap://localhost:389 -a  << EOF
> dn: uid=user1,ou=People,dc=example,dc=com
> objectClass: inetUser
> objectClass: top
> objectClass: person
> objectClass: organizationalPerson
> objectClass: inetOrgPerson
> cn: user1
> sn: user1
> uid: user1
> EOF
adding new entry "uid=user1,ou=People,dc=example,dc=com"


$ ldapmodify -D 'cn=Directory Manager' -w Secret123 -H ldap://localhost:389 <<EOF
> dn: uid=user1,ou=people,dc=example,dc=com
> changetype: modrdn
> newrdn: uid=useršľčť
> deleteoldrdn: true
> EOF
modifying rdn of entry "uid=user1,ou=people,dc=example,dc=com"
ldap_rename: Constraint violation (19)
	additional info: The value is not 7-bit clean: 


Marking as VERIFIED

Comment 4 errata-xmlrpc 2015-03-05 09:33:20 UTC
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.

https://rhn.redhat.com/errata/RHSA-2015-0416.html