Bug 870519 - Unable to specify sslsocket port in advanced configuration during installation of server
Unable to specify sslsocket port in advanced configuration during installatio...
Status: NEW
Product: RHQ Project
Classification: Other
Component: Installer (Show other bugs)
All All
unspecified Severity medium (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
Depends On:
  Show dependency treegraph
Reported: 2012-10-26 14:05 EDT by Larry O'Leary
Modified: 2012-10-26 14:05 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Larry O'Leary 2012-10-26 14:05:21 EDT
Description of problem:
If enabling sslsocket for agent-to-server communication during server install, you can not set the sslsocket port (rhq.communications.connector.bind-port).

There is no field for this property. 

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

How reproducible:

Steps to Reproduce:
1. Run the server installer
2. Check *Show Advanced Settings* at the top of the install page
3. Set Incoming Agent Communications Transport to sslsocket
4. ... this is where you would set the sslsocket but there's no field for this
Actual results:
No place to specify sslsocket port.

Expected results:
A field where sslsocket port can be specified. Specifically, a field that maps to rhq.communications.connector.bind-port with a default value of 7080 for socket, 7443 for sslservlet, and 55555.

Additional info:
The only way to set this value is to edit rhq-server.properties prior to running the install. However, this doesn't make sense seeing that sslsocket is a valid value in the install page for rhq.communications.connector.transport.

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