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 1382856 - ldapjdk fails to parse ldap url with no host:port
Summary: ldapjdk fails to parse ldap url with no host:port
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ldapjdk
Version: 7.3
Hardware: All
OS: All
urgent
urgent
Target Milestone: rc
: ---
Assignee: mreynolds
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks: 1388500
TreeView+ depends on / blocked
 
Reported: 2016-10-07 21:52 UTC by Noriko Hosoi
Modified: 2017-08-01 21:09 UTC (History)
6 users (show)

Fixed In Version: ldapjdk-4.19-1.el7
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of: 1376823
: 1388500 (view as bug list)
Environment:
Last Closed: 2017-08-01 21:09:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2078 0 normal SHIPPED_LIVE ldapjdk bug fix and enhancement update 2017-08-01 18:37:13 UTC

Comment 1 mreynolds 2016-10-07 22:21:29 UTC 
This is now fixed/pushed in upstream mozilla via https://bugzilla.mozilla.org/show_bug.cgi?id=1308541

Now we need Matt to respin it in koji/brew.
Comment 4 Marc Sauton 2016-10-25 01:02:55 UTC 
GSS Approved Z-Stream
Comment 7 Sumedh Sidhaye 2017-05-05 08:11:33 UTC 
[root@pki1 ~]# rpm -qi ldapjdk
Name        : ldapjdk
Epoch       : 0
Version     : 4.19
Release     : 1.el7
Architecture: noarch
Install Date: Friday 05 May 2017 01:31:47 AM EDT
Group       : Development/Java
Size        : 347548
License     : MPLv1.1 or GPLv2+ or LGPLv2+
Signature   : RSA/SHA256, Saturday 11 March 2017 03:14:20 PM EST, Key ID 199e2f91fd431d51
Source RPM  : ldapjdk-4.19-1.el7.src.rpm
Build Date  : Saturday 11 March 2017 02:47:33 PM EST
Build Host  : ppc-042.build.eng.bos.redhat.com
Relocations : (not relocatable)
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
Vendor      : Red Hat, Inc.
URL         : http://www-archive.mozilla.org/directory/javasdk.html
Summary     : The Mozilla LDAP Java SDK
Description :
The Mozilla LDAP SDKs enable you to write applications which access,
manage, and update the information stored in an LDAP directory.

Steps to verify:

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


Actual Result: No empty pop up is displayed.
Comment 8 errata-xmlrpc 2017-08-01 21:09:05 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-2017:2078
Note You need to log in before you can comment on or make changes to this bug.