Right now, the user has to pass in -D props to the CLI in order to be able to talk to the server over SSL, even if the user just wants to use encryption and have the CLI auto-gen a self-signed cert. We should enable this out of box - if the user didn't set any props, provide some sensible defaults so the CLI will be able to self-sign an auto-gen cert.
no need to mess with environment vars if you are on a Sun JRE and you only need a self-signed auto-generated cert.
to test: just start the out-of-box CLI (don't mess with any env files or set special props) and login over SSL: login rhqadmin rhqadmin localhost 7443 it should connect. then go to your CLI's data/ directory and confirm you have a keystore.dat file created.
This is verified, login was successful and the keystore.dat gets created successfully in data/ directory. [root@dhcp6-150 bin]# ./rhq-cli.sh RHQ - RHQ Enterprise Remote CLI 1.3.0-SNAPSHOT unconnected$ login rhqadmin rhqadmin localhost 7443 Remote server version is: 1.3.0-SNAPSHOT(4856) Login successful rhqadmin@localhost:7443$quit [root@dhcp6-150 bin]# cd .. [root@dhcp6-150 rhq-remoting-cli-1.3.0-SNAPSHOT]# ls bin conf data lib logs [root@dhcp6-150 rhq-remoting-cli-1.3.0-SNAPSHOT]# cd data [root@dhcp6-150 data]# ls keystore.dat
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2304