I'm trying to integrate Jira 4.4.3 with Jenkins 1.456 and I'm completely stuck. Jenkins keeps getting a 403 error when it tries to communicate with Jira. This is odd because both are using the same Crowd server for authentication, hosted on the same server as the Jira instance.
I've tried adding an Application Link between Jira and Jenkins, but the process baffles me. Jenkins can only be added as a generic application using OAuth for incoming authentication. I have been unable to get Jira to accept a Public Key for the Jenkins app. What little information I've found suggests that the Public Key should be a standard 1024-bit RSA public key generated with sha1. I generated a public key for the server but when I paste it into Jira's Oauth configuration screen I always get this error: "Must be a valid public key. java.security.InvalidKeyException: IOException: algid parse error, not a sequence".
Another issue is that I have been completely unable to figure out how to obtain a Consumer Key from the Jenkins application. I am starting to suspect that Jenkins simply doesn't support OAuth.
I kept getting the invalid key error as well until I stumbled upon this tutorial:
Which provided the following example on creating the keys:
openssl genrsa -out jira.pem 1024
openssl rsa -in jira.pem -pubout -out jira.pub
This article no longer says anything of the sort
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@beeplogic's command worked for me for setting up a generic OAUTH application link on JIRA v6.5-OD-08-001
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having the same issue. @beeplogic's solution didn't work. Were you able to resolve the issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.