We've been using Confluence CLI successfully for about 6 months then several week ago when our JIRA-ON-DEMAND was upgraded, Confluence CLI stop working with the following error:
Unable to log in to server: http://osiinc.jira.com/confluence/rpc/soap-axis/confluenceservice-v1 with user: automation.
Cause: (301)Moved Permanently
I tried "atlassian-cli-2.6.0" but had no success. When I put the url http://osiinc.jira.com/confluence/rpc/soap-axis/confluenceservice-v1" in the browser, I get the following:
Hi there, this is an AXIS service!
Perhaps there will be a form for invoking the service here...
Anyone have this problem!
Try using https in the URL instead of http. All Atlassian OnDemand instances require https connections for security reasons, and redirect http URLs to https ones. It looks like the CLI is not following the redirection, but if you give it https in the first place, that should work.
I'm using "atlassian-cli-2.6.0" downloaded from url
This CLI was developed by by Bob Swift, and I using it to post pages to our
space. Is this something that Bob Swift should fix?
Well, yes I think the CLI should be fixed to follow redirects, but what I mean is that if you pass the URL with https to the CLI in the first place, that should work as-is. So what I mean is to pass "https://osiinc.jira.com/confluence/rpc/soap-axis/confluenceservice-v1" when you call the CLI program.
We running jdk1.6.0_11
Our confluence.sh file contains the following:
java -jar /opt/atlassian-cli-2.6.0/lib/confluence-cli-2.6.0.jar --server http://osiinc.jira.com/confluence --user automation --password !automation+! "$@"
The command executed to push the page to our space is:
/opt/atlassian-cli-2.6.0/confluence.sh --action storePage --space NX --title "vcds_6.4.0 Build Report" --file /opt/osi_confluence/6.4/vcds_6.4.0 --parent 6.4
Where in my command line do I pass the URL with "https://osiinc.jira.com/confluence/rpc/soap-axis/confluenceservice-v1"
Created case "ACLI-71" assigned to Bob Swift. He was able to reproduce the problem on his on demand site. He said to use https and now it works. When I tried it earlier after you suggested it, it didn't work. Not sure what changed after he got involved.
The performance is real slow compared to when it used to work with http. Takes about 6 seconds to do the following command:
jira --action getServerInfo
Can something be done to improve the performance?
I am having the same issue:
./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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs