How to integrate Atlassian Jira with Liferay portal using OAuth authentication

Other Questions Jira
1

I’m trying to connect Jira version 4.2 with my Liferay 6.1 beta 4 portal. I created a gadget from Jira and put it on a Liferay page. Then I configured the consumer keys and public keys in the Jira admin panel for my Liferay setup. I used the same key values in the OpenSocial portlet configuration.

When I test this on my local development environment, I keep getting this OAuth error message:

{
  "oauthError": "UNKNOWN_PROBLEM",
  "body": "",
  "oauthErrorText": "Cannot find consumer key\n\n==== Request details:\nGET /rest/gadget/1.0/currentUser?cacheBuster=1323789929397\n\nHost: 127.0.0.1:9080\nX-Shindig-AuthType: oauth\nX-Forwarded-For: 127.0.0.1\nX-shindig-dos: on",
  "DataHash": "abc123def456ghi789jkl012mn",
  "rc": 403
}

Did anyone manage to get Jira and Liferay working together with OAuth? What am I missing in the setup process?

2

That UNKNOWN_PROBLEM OAuth error with legacy versions usually means certificate validation issues, not just consumer key problems. I hit this exact thing about five years ago. Your Jira’s rejecting the OAuth request because the SSL handshake fails during auth. Check if Liferay’s certificate is properly set up in Jira’s truststore. Since you’re on localhost, make sure both apps use the same protocol - either HTTP or HTTPS for both. Mixed protocols break OAuth flows in older Atlassian versions. I see Shindig in your request headers, so verify your OpenSocial container config matches what Jira expects. Try clearing the OAuth token cache in both apps - sometimes that fixes stuck authentication states.

3

Those versions are ancient and OAuth debugging between them is a nightmare. Been there, done that.

You’re building a bridge between two legacy systems that hate each other. Fix the consumer key issue and you’ll just hit more OAuth problems.

I ditched direct integration entirely. Used Latenode as a middleman - it handles the OAuth dance between Jira and Liferay without the headaches.

Set up a workflow that authenticates with Jira, grabs your data, then pushes it to Liferay through the API. No more gadget config nightmares or consumer key issues.

You get better control over data flow and can transform stuff if needed. The OAuth actually works.

Check it out at https://latenode.com

4

yeah, make sure ur consumer key is spot on. even a tiny space can mess things up. also, look at the app link settings in jira, sometimes a restart does wonders!

5

That error means your Jira instance can’t find the consumer key during OAuth. I hit the same issue last year when setting this up. Sure, double-check your consumer key, but also verify your Liferay server’s IP matches what’s configured in Jira’s application links. That localhost address in your error trace screams networking problems between the services. Make sure your OAuth callback URL in Jira points to the right Liferay instance. Jira 4.2 is picky about URL formatting - no trailing slashes or extra parameters. Also confirm OAuth is enabled in your Jira instance and the consumer key has gadget access permissions.

6

check ur jira logs when the oauth call happens - probably getting blocked at the network level. had similar setup and the issue was firewall dropping requests between services. also verify ur opensocial gadget xml has the right oauth service name that matches jira config