nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Not able to login using JSON-RPC

stefanmeisnerlarsen

I have problems logging in using the JSON-RPC service on JIRA OnDemand. As I understand, this service should be available, and the system settings indicates this too.

I send:

{"id":123,"jsonrpc":"2.0","method":"login","params":["stefan@meisner-larsen.dk","mypassword"]}

replacing mypassword with the correct to the url:

http://ayeoaps.atlassian.net:80/jira/rpc/json-rpc/jirasoapservice-v2

and keep getting 404 response back.

Replacing http with https results in 403 response instead.

Any help appreciated!

/Stefan

Accepted answers

Michael Knight

You should be using HTTPS and not forcing port 80, since all OnDemand instances are served through HTTPS (on the conventional port 443). This snippet should work for you:

#!/bin/bash
URL='https://ayeoaps.atlassian.net/rpc/json-rpc/jirasoapservice-v2'
DATA='
{
    "jsonrpc" : "2.0",
    "method" : "login",
    "params" : ["admin","password"],
    "id" : 12345
}
'
curl -H 'Content-type: application/json' -d "$DATA" $URL

All comments

JamieA

Think you're muddling the soap and json rpc urls, but don't have the correct url to hand.

stefanmeisnerlarsen

I have tried the following URL (without 'jira' after hostname) with the same result:

http://ayeoaps.atlassian.net/rpc/json-rpc/jirasoapservice-v2

Azwandi Mohd Aris

You might want to try with the correct URL - http://ayeoaps.atlassian.net/rest/auth/1/session

More info at http://docs.atlassian.com/jira/REST/latest/#id2474849

stefanmeisnerlarsen

Jamie, I got the URL from the documentation: https://developer.atlassian.com/display/JIRADEV/JIRA+JSON-RPC+Overview

The jirasoapservice-v2 is aparently because it a wrapper around the SOAP interface

JamieA

Oh yeah, I keep being surprised about this new soap-rpc bridge, then forgetting about it, then getting surprised again. My bad.

Dieter

Are you sure you can use the email address as parameter name? Could you try it using the user name

Michael Knight

You should be using HTTPS and not forcing port 80, since all OnDemand instances are served through HTTPS (on the conventional port 443). This snippet should work for you:

#!/bin/bash
URL='https://ayeoaps.atlassian.net/rpc/json-rpc/jirasoapservice-v2'
DATA='
{
    "jsonrpc" : "2.0",
    "method" : "login",
    "params" : ["admin","password"],
    "id" : 12345
}
'
curl -H 'Content-type: application/json' -d "$DATA" $URL

stefanmeisnerlarsen

Thanks Michael. Actually i did try the https url in your script, the problem was that I did a PUT not a POST which was then answered with a 403 Forbidden, which seems OK. But trying your script with success made me realize what the real problem was :-)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-cloud

json