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.

Bug 1388500

Summary: ldapjdk fails to parse ldap url with no host:port
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: ldapjdkAssignee: Matthew Harmsen <mharmsen>
Status: CLOSED ERRATA QA Contact: Asha Akkiangady <aakkiang>
Severity: urgent Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: urgent    
Version: 7.3CC: enewland, mharmsen, mmuehlfe, mreynolds, msauton, nhosoi, nkinder, ssidhaye
Target Milestone: rcKeywords: Regression, ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: ldapjdk-4.18-16.el7_3 Doc Type: Bug Fix
Doc Text:
A regression introduced in an earlier bug fix caused ldapjdk to fail in parsing the LDAP URL, when the "host:port" part was not specified. A patch has been provided to fix the problem and as a result, ldapjdk now correctly parses LDAP URLs in the described situation.
Story Points: ---
Clone Of: 1382856 Environment:
Last Closed: 2016-12-06 17:04:35 UTC Type: ---
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: 1382856    
Bug Blocks:    
Attachments:
Description Flags
mozilla ldapjdk fix none

Description Marcel Kolaja 2016-10-25 13:55:59 UTC
This bug has been copied from bug #1382856 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 5 mreynolds 2016-10-31 17:18:04 UTC
Created attachment 1215867 [details]
mozilla ldapjdk fix

Comment 9 Sumedh Sidhaye 2016-11-08 12:38:37 UTC
Verified with the following builds:

ldapjdk-4.18-16.el7_3.noarch
389-admin-console.noarch 1.1.12-2.el7dsrv 

Followed steps mentioned in bug #1376823

First I tried it with ldapjdk-4.18-15.el7.noarch and 389-admin-console.noarch 1.1.10-1.el7dsrv where I followed the steps given below:

1. Open the DS console
2. Create a new role
3. Type Name and Description for role
4. Click on Members tab

Actual Result: A pop-up without any error message is shown.

I re-ran the above steps with ldapjdk-4.18-16.el7_3.noarch and 389-admin-console.noarch 1.1.12-2.el7dsrv, now I do not see the empty pop up box anymore.

Actual Result: No empty pop up is displayed.

Hence marking this verified.

Comment 14 errata-xmlrpc 2016-12-06 17:04:35 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/RHBA-2016-2880.html