Bug 1751173 - RHDS WebUI - Need to validate the port number when creating a suffix referral.
Summary: RHDS WebUI - Need to validate the port number when creating a suffix referral.
Alias: None
Product: Red Hat Directory Server
Classification: Red Hat
Component: cockpit-389-ds
Version: 11.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: mreynolds
QA Contact: RHDS QE
Depends On:
TreeView+ depends on / blocked
Reported: 2019-09-11 10:35 UTC by Têko Mihinto
Modified: 2019-11-06 12:42 UTC (History)
7 users (show)

Fixed In Version: 389-ds-base-
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-11-06 12:42:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:3731 None None None 2019-11-06 12:42:45 UTC

Description Têko Mihinto 2019-09-11 10:35:15 UTC
Description of problem:
One can create a suffix referral with an invalid port number for the referred LDAP server.

Version-Release number of selected component (if applicable):
# rpm -qa | grep 389-ds

How reproducible:

Steps to Reproduce:
1. Create a suffix
2. Select the "Database" tab and choose a suffix
3. Click on "Create Referral"
4. Use invalid characters for the port number
5. Click on "Create Referral". The suffix referral will be created with the invalid port number.

Actual results:
Invalid referral ( incorrect port number ) is created.

Expected results:
Prevent the user to create invalid referral.

Additional info:

Comment 3 Viktor Ashirov 2019-10-29 21:41:21 UTC
Builds tested:

When I enter letters instead of numbers, and then save the referral, I get the error message:
Invalid port number, please use a number between 1 and 65535

I think we should not accept non-numeric characters in the first place. But that can be done as part of ReactJS refactor.

Marking as VERIFIED.

Comment 5 errata-xmlrpc 2019-11-06 12:42:36 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.


Note You need to log in before you can comment on or make changes to this bug.