Description of problem: The built-in "login" command in the interactive CLI supports specifying the transport for the CLI-server communication as its 5th parameter: login username pass host 1234 sslservlet would log in as user "username" with given password on host "host", port 1234 over ssl. This is not possible using the predefined "rhq" object that otherwise exposes the login and logout commands. This makes it impossible for the non-interactive CLI scripts to manually log in using a specific transport. Note that the transport is guessed if missing from the port number - any port "ending" with 443 is supposed to be an sslservlet, otherwise servlet is tried. Version-Release number of selected component (if applicable): 4.7.0-SNAPSHOT How reproducible: always Steps to Reproduce: 1. Configure RHQ server to listen on a non-standard port (say 1234) over HTTPS. 2. Try to connect to it through CLI's builtin "login" command 3. Try the same using the "rhq.login()" method Actual results: Unable to log in using the rhq.login() method Expected results: there should be the possibility to specify the transport with the rhq.login() method Additional info:
commit 755ea862750217ec1fa72e215a5b4b05f8678275 Author: Lukas Krejci <lkrejci> Date: Mon Mar 18 14:33:33 2013 +0100 [BZ 922687] - Enabling login on non-std SSL ports in non-interactive CLI Added an overloaded method to be able to specify the transport used for connection.
Bulk closing of issues in old RHQ releases that are in production for a while now. Please open a new issue when running into an issue.