Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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://access.redhat.com/errata/RHBA-2018:0811
Description of problem: We can break the nsds5replicaid attribute rules (it should be 1 to 65534 for suppliers) if we'll try to modify the existing replication entry. Version-Release number of selected component (if applicable): 389-ds-base-1.3.6.1-5.el7.x86_64 How reproducible: Always Steps to Reproduce: [1] Install an instance [2] Add a replica entry: [root@qeos-175 ds]# ldapmodify -a -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config cn: replica nsDS5Flags: 1 nsDS5ReplicaBindDN: cn=sync user,cn=config nsDS5ReplicaId: 7 nsDS5ReplicaRoot: dc=example,dc=com nsDS5ReplicaType: 3 objectClass: top objectClass: nsDS5Replica objectClass: extensibleobject adding new entry "cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" [3] Check the entry: [root@qeos-175 ds]# ldapsearch -h localhost -p 389 -D "cn=Directory manager" -w Secret123 -b "cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" # replica, dc\3Dexample\2Cdc\3Dcom, mapping tree, config dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config cn: replica nsDS5Flags: 1 nsDS5ReplicaBindDN: cn=sync user,cn=config nsDS5ReplicaId: 7 nsDS5ReplicaRoot: dc=example,dc=com nsDS5ReplicaType: 3 objectClass: top objectClass: nsDS5Replica objectClass: extensibleobject nsState:: BwAAAAAAAADycuJYAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAA== nsDS5ReplicaName: 65766987-188711e7-80a2fa60-3a60cc96 nsds5ReplicaChangeCount: 0 nsds5replicareapactive: 0 [4] Set nsDS5ReplicaId to some wrong_id format: [root@qeos-175 ds]# ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config changetype: modify replace: nsDS5ReplicaId nsDS5ReplicaId: wrong_id modifying entry "cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" [5] Check the entry: [root@qeos-175 ds]# ldapsearch -h localhost -p 389 -D "cn=Directory manager" -w Secret123 -b "cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" # replica, dc\3Dexample\2Cdc\3Dcom, mapping tree, config dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config cn: replica nsDS5Flags: 1 nsDS5ReplicaBindDN: cn=sync user,cn=config nsDS5ReplicaId: wrong_id nsDS5ReplicaRoot: dc=example,dc=com nsDS5ReplicaType: 3 objectClass: top objectClass: nsDS5Replica objectClass: extensibleobject nsState:: BwAAAAAAAADycuJYAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAAAAAA== nsDS5ReplicaName: 65766987-188711e7-80a2fa60-3a60cc96 nsds5ReplicaChangeCount: 0 nsds5replicareapactive: 0 Actual results: It is possible to set bogus replica id to the existing replica entry Expected results: Operation error should happen when we try to set bogus replica id Additional info: - Operation error happens with a wrong replica id when we are creating the replica entry initially. - It is impossible to set nsDS5ReplicaId to something in the second time: [root@qeos-175 ds]# ldapmodify -h localhost -p 389 -D "cn=Directory manager" -w Secret123 dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config changetype: modify replace: nsDS5ReplicaId nsDS5ReplicaId: 8 modifying entry "cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config" ldap_modify: Operations error (1) additional info: replica type is already 2 - not changing