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.
Bug 1633488 - fixup-memberof.pl -D cn=<> -w - -b <> -P LDAP fails with ldap_start_tls error
Summary: fixup-memberof.pl -D cn=<> -w - -b <> -P LDAP fails with ldap_start_tls error
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.5
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 7.7
Assignee: Matus Honek
QA Contact: RHDS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-27 06:58 UTC by amitkuma
Modified: 2020-09-13 22:17 UTC (History)
11 users (show)

Fixed In Version: 389-ds-base-1.3.9.1-1.el7
Doc Type: Bug Fix
Doc Text:
Cause: Incorrect internal setting of the protocol requested on the command line. Consequence: The requested protocol is not respected. Fix: Change the code so that the requested protocol is respected. Result: fixup-memberof.pl works as expected with -P LDAP argument.
Clone Of:
Environment:
Last Closed: 2019-08-06 12:58:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 3193 0 None None None 2020-09-13 22:17:39 UTC
Red Hat Product Errata RHBA-2019:2152 0 None None None 2019-08-06 12:59:06 UTC

Description amitkuma 2018-09-27 06:58:02 UTC 
Description of problem:
If we execute the following:

/usr/lib64/dirsrv/slapd-<>/fixup-memberof.pl -D cn=<> -w - -b <> -P LDAP

We get this error:

ldap_start_tls: Connect error (-11)
	additional info: TLS: hostname does not match CN in peer certificate
Failed to add task entry "cn=memberOf_fixup_2018_9_26_12_46_54, cn=memberOf task, cn=tasks, cn=config" error (1)

It makes no sense because we have specified the option "-P LDAP" in order not to use startTLS.

Customer have configured in the server a certificate with different name because the server is behind a load balancer and all the client request works with that different name.

If we use the same option (-P LDAP) with the script "/usr/lib64/dirsrv/slapd-<>/db2bak.pl" works fine and it uses LDAP without startTLS.

Version-Release number of selected component (if applicable):
RHDS 10
# rpm -qa | grep 389
389-admin-console-1.1.10-1.el7dsrv.noarch
389-adminutil-1.1.22-1.el7dsrv.x86_64
389-admin-1.1.42-1.el7dsrv.x86_64
389-ds-console-1.2.12-1.el7dsrv.noarch
389-admin-console-doc-1.1.10-1.el7dsrv.noarch
389-ds-base-libs-1.3.3.1-20.el7_1.x86_64
389-ds-base-1.3.3.1-20.el7_1.x86_64
389-ds-console-doc-1.2.12-1.el7dsrv.noarch
389-console-1.1.8-1.el7dsrv.noarch


How reproducible:
All times

Steps to Reproduce:
1. Provided in description
2.
3.

Actual results:
fixup-memberof.pl fails with startTLS when "-P LDAP" is specified.

Expected results:
fixup-memberof.pl should not fail with startTLS when "-P LDAP" is specified.

Additional info:
none
Comment 1 amitkuma 2018-09-27 06:59:14 UTC 
Customer also provided an solution:

I think I have solved this issue editing the script "/usr/sbin/fixup-memberof.pl". In line 80 I have changed this:
$info[9] = $protocol;

By this:
$info{protocol} = $protocol;

Now the execution works fine as it uses LDAP instead of stratTLS.
Comment 3 amitkuma 2019-01-03 07:22:47 UTC 
Dear Matus Honek,
Is there any update on bugzilla.
Amit
Comment 7 Akshay Adhikari 2019-05-02 13:54:33 UTC 
Build Tested: 389-ds-base-1.3.9.1-5.el7.x86_64

Steps:

1) Create a user.

2) Created a group.

3) Added the user to the group.

4) Enabled memberof plugin 

5) Restarted the server. (Only works after restart)

6) run fixup-memberof.pl -Z slapd-aadhikar -D "cn=Directory Manager" -w password -b "dc=example,dc=com" -P LDAP
Successfully added task entry "cn=memberOf_fixup_2019_5_2_8_31_6, cn=memberOf task, cn=tasks, cn=config"

fixup-memberof.pl does not fails with startTLS when "-P LDAP" is specified.

Hence, marking it as VERIFIED.
Comment 9 errata-xmlrpc 2019-08-06 12:58:51 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://access.redhat.com/errata/RHBA-2019:2152
Note You need to log in before you can comment on or make changes to this bug.