JIRA OAuth Configuration

I am trying to file Tickets with a Google Docs Script using OAuth authentification. But I am stuck in the configuration.

I did configure an application link with an incoming authentication. I did set the Consumer Name, the Consumer Key and the Public Key.

Now I am trying to access JIRA from my Google Docs Script using the URLFetchApp class. I can register an oauth configuration. I did set all the URLs:

AccessTokenUrl: http://myhost/plugins/servlet/oauth/access-token

requestTokenUrl: http://myhost/plugins/servlet/oauth/request-token

authorizationUrl: http://myhost/plugins/servlet/oauth/authorize

But what do I have to set as Consumer Key and especially Consumer Secret? I used the Value of Consumer Key as Consumer Key. Sounds good. But I don't know what to use as Consumer Secret. Neither the Public Key, the matching Private Key nor the Consumer Name worked. The bad thing: I cannot get a proper Error Message from the Google Docs Script.

4 answers

Hello,

When setting up OAuth authentication in JIRA, you will need a certificate file to perform the "OAuth dance". If Google Docs didn't provide it, you can create a certificate file using OpenSSL and apply it for both -- JIRA and Google Docs. It will be your Public and Private Keys.

Best regards,
Lucas Timm

Hi Lucas,

thanks for your answer. I did create a Key-Pair and pasted the Content of the public-key file (without ----- BEGIN PUBLIC KEY ----- and ----- END PUBLIC KEY ----- and linebreaks) into the public key field in JIRA. But at Google Docs side I cannot provide a key-file. I can provide a "Consumer Key" and a "Consumer Secret". So. What's the Key and what's the Secret? And why can I configure 3 fields "Consumer Key", "Consumer Name" and "Public Key" in JIRA? How do these filds match?

Best regards, Martin

Martin,

Did you ever fix this issue. Atlassian is terrible for documentation on this, so i thought i would share my thoughts after trying to implement it for the last 10 hours. It is my first time at oAuth and experienced users might have known from the outset that because JIRA uses RSA-SHA1 signing, you do not need a consumer secret key. Wow so that would have been nice to know...

I tried everything you had done too.

Basically i want to leave an answer as i stubbled across this whilst stuggling myself and would have saved a lot of time if somebody actually made the effort to help.

Remeber that Private key you have? This needs to be used to sign the request that gets sent to the JIRA server. JIRA then uses the public key you gave it to decode the request and boom you have made the connection.

If you are using (like me) the oauth-php source downloaded from googlecode. It includes the functionallity to sign your requests using RSA-SHA1 but its not fully implemented. All i did was find the class and where it calls the Private Key, paste it in.

Now i can make requests like a breeze and it only took all *sigh* day.

can you provide a sample code of your implementation, i already use oauth-php library but can't get it to work!!

Hello William, can you show an example of your implementation, i've been banging my head to the desk for a couple of days, so far i've got the request token :(

Hi William, I have same problem, I have private key and I need to use it with consumer key to implement OAuth on Jira. is it possible for you to show the code? thanks.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Friday in Jira Service Desk

Looking for anyone who has switched from Zendesk to Jira Service Desk

Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk!   We’d love to hear your thoughts on the pros and ...

36 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you