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:
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