Bug 2090393

Summary:	Add a warning when port numbers are set to zero.
Product:	Red Hat Directory Server	Reporter:	Têko Mihinto <tmihinto>
Component:	cockpit-389-ds	Assignee:	mreynolds
Status:	CLOSED ERRATA	QA Contact:	RHDS QE <ds-qe-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	12.0	CC:	afarley, bsmejkal, gkimetto, hkhot, ldap-maint, mreynolds
Target Milestone:	---	Keywords:	Triaged
Target Release:	dirsrv-12.1
Hardware:	x86_64
OS:	All
Whiteboard:
Fixed In Version:	redhat-ds-12-9010020220729141346.12_1_910	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-12-06 15:44:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Têko Mihinto 2022-05-25 16:32:22 UTC

Description of problem:
The "Create New Server Instance" allows to use 0 ( even multiple zeroes are accepted ).
The instance creation goes fine and the normal port is set to 0 while the TLS port is set to the default value ( 636 ).

It would be nice to add a warning to let the user know that :
* TLS port will be set to 636
* Access over the normal port will be disabled.

Version-Release number of selected component (if applicable):

$ cat /etc/redhat-release 
Red Hat Enterprise Linux release 9.1 Beta (Plow)
$
$ rpm -qa | grep 389-ds
389-ds-base-libs-2.0.14-7.module+el9dsrv+14845+69b2f526.x86_64
389-ds-base-2.0.14-7.module+el9dsrv+14845+69b2f526.x86_64
cockpit-389-ds-2.0.14-7.module+el9dsrv+14845+69b2f526.noarch
$

How reproducible:
Always ( as long as port 636 is available ).

Steps to Reproduce:
1. Launch the "Create New Server Instance" wizard
2. Use 0 for the ports
3. Create the instance

Actual results:
The instance is created with ports 0 and 636.

Expected results:
Add a warning prior to create the instance.

Additional info:

Comment 6 errata-xmlrpc 2022-12-06 15:44:42 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 (redhat-ds:12 bug fix and enhancement update), 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-2022:8836