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.
- converting configuration from old slapd.conf to new slapd.d while 'constraint' overlay is used
- 'constraint_attribute' of 'size' or 'count' type is converted to 'olcConstraintAttribute' while missing the 'value' part of the settings
- patch was applied to target the 'constraint_attribute' settings conversion
- conversion of 'constraint' overlay settings to the new style of configuration converts all 'constraint_attribute' values correctly
Created attachment 513620[details]
Slapd configuration file for slaptest
Description of problem:
Bad slaptest translate for constraints size and count. Slaptest encode only size or count parametr without value.
Version-Release number of selected component (if applicable):
openldap-servers-2.4.23-15.el6.
How reproducible:
always
Steps to Reproduce:
slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d/
Actual results:
File /etc/openldap/slapd.d/cn\=config/olcDatabase\=\{1\}bdb/olcOverlay\=\{0\}constraint.ldif has bad base64 decoced olcConstraintAttribute
objectClass: olcOverlayConfig
objectClass: olcConstraintConfig
olcOverlay: {0}constraint
olcConstraintAttribute:: anBlZ1Bob3RvIHNpemUg
olcConstraintAttribute:: c24gY291bnQg
structuralObjectClass: olcConstraintConfig
entryUUID: 23c9fe22-458b-1030-8c85-1b3b9d785baa
creatorsName: cn=config
createTimestamp: 20110718131106Z
entryCSN: 20110718131106.023140Z#000000#000#000000
modifiersName: cn=config
modifyTimestamp: 20110718131106Z
Command output of decoded olcConstraintAttribute:: c24gY291bnQg
echo "c24gY291bnQg" | base64 -d
result: sn count
Expected results:
Command output of decoded olcConstraintAttribute::
sn count 5
Additional info:
Bug was reported as ITS#6986 (http://www.openldap.org/its/index.cgi/Documentation?id=6181)
Similar problem with extra parametr restrict. Restrict must be in "" and the prefix "restrict=" is repeated. Problem was reported as ITS#6181.
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:
- converting configuration from old slapd.conf to new slapd.d while 'constraint' overlay is used
- 'constraint_attribute' of 'size' or 'count' type is converted to 'olcConstraintAttribute' while missing the 'value' part of the settings
- patch was applied to target the 'constraint_attribute' settings conversion
- conversion of 'constraint' overlay settings to the new style of configuration converts all 'constraint_attribute' values correctly
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/RHBA-2011-1514.html