When trying to connect to an SaaS HP ALM server from Jenkins on a RHEL7 box via a Windows Slave, the connection fails and the log contains the following info:
13:32:35 Started by user Josh Privett
13:32:35 Building remotely on alm_connection in workspace C:\Jenkins\workspace\Run_HP_ALM_Tests
13:32:35 Start login to ALM server.
13:32:36 Login to ALM Server at https://xxxxxxxxxxx/qcbin/ failed. Status Code: 302
13:32:36 Empty Results
13:32:36 Result Status: UNSTABLE
13:32:36 Build step 'Execute HPE tests using HPE ALM Lab Management' changed build result to UNSTABLE
13:32:37 Finished: UNSTABLE
We found that this was an issue in the past with https but it had allegedly been fixed in 5.2. We have confirmed that the credentials are correct for logging in. What are we doing incorrectly?