Help with JIRA CLI setup..

Question

Hi,

When I try using the jira CLI command I get this error. I am trying to set up JIRA CLI:

./jira.sh --server "https://hofdvjira1.searshc.com" --user XXXXX --password XXXXXX --action getServerInfo

Unable to log in to server: https://hofdvjira1.searshc.com/rpc/soap/jirasoapservice-v2 with user: rsen0.

Cause: ; nested exception is: java.net.ConnectException: Connection refused

The user id and password do exists and I have also created the default user id and password automation and also tried with that.

./jira.sh --server "https://hofdvjira1.searshc.com:1643" --user automation --password automation --action getServerInfo

Unable to log in to server: https://hofdvjira1.searshc.com:1643/rpc/soap/jirasoapservice-v2 with user: automation.Cause: (400)Bad Request

The entry in the jira.sh file I have is :

java -jar `dirname $0`/lib/jira-cli-2.5.0.jar "$@"

The JIra CLI version is 2.5.0. JIRA version is 4.2.1-b588. Server is Linux 2.6.18. Soap API is already enabled on our JIRA.

Joe Clark · Answer

I don't think so, sorry - when you execute 'java', are you using the same java executable being used by JIRA? Presumably the JIRA Server JVM has to import your certificate from a trust store somewhere, so you should be able to pioint your CLI jvm at the same one :-)

Romit Sen · Answer

Is there a way to set up the JVM to not check any certificates (since I am runnign this on the Jira Server itself)?

for example this works fine:

wget --no-check-certificate https://hofdvjira1.searshc.com:1643/jira/secure/Dashboard.jspa

--2012-08-20 10:23:01--  https://hofdvjira1.searshc.com:1643/jira/secure/Dashboard.jspa
Resolving hofdvjira1.searshc.com... 151.149.119.95
Connecting to hofdvjira1.searshc.com|151.149.119.95|:1643... connected.
WARNING: cannot verify hofdvjira1.searshc.com's certificate, issued by `/C=US/ST=XXXXX/L=XXXXXXXXXX/O=XXX/CN=XXX':
  Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `Dashboard.jspa.3'

[ <=>                                   ] 33,290      --.-K/s   in 0.001s

Joe Clark · Answer

It's possible that your local JVM is not configured to trust the SSL certificate being presented by your JIRA server - do you know if your JIRA server is using a self-signed certificate or a certificate issued from a third-party Certification Authority?

This page might give you some hints to trouble-shooting it: https://secure.marumoto.us/motowiki/tiki-index.php?page=Test+a+Java+SSL+connection