Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Inaccurate OAuth Guide

Hello,

I have been using the OAuth guide provided here: https://developer.atlassian.com/server/jira/platform/oauth/

It states that in order to authenticate I have to generate a public-private key pair and make a configuration in Jira and send it in my request for temporary token.
This command is supposed to be generating this key pair: 

openssl genrsa -out jira_privatekey.pem 1024

This was correct a few months ago. However for quite some time now, the implementation has been changed apparently and this guide is outdated.
If using this same key now, Jira will return an exception like the following:

Signature length not correct: got 128 but was expecting 256.

Please fix this guide by replacing the command with the following one:
openssl genrsa -out jira_privatekey.pem 2048

This one generates public-private key pair of 2048bit. The rest of the implementation remains the same.


Also there have been some deprecated Libraries used in the code implementation of the Jira OAuth client.


Please fix them as well.

 

Best Regards,
Martin

0 comments

Comment

Log in or Sign up to comment