I’m having trouble setting up OAuth authentication between my Liferay portal and Jira instance. Here’s what I’ve done so far:
First, I generated RSA keys using the keytool utility and saved the certificate as jiraAuth.pem. I put this file in the liferay-home/opensocial/ directory.
Next, I set up the Application Links in Jira’s incoming authentication settings:
Public key: copied the public key content from my jiraAuth.pem file
The public key field became disabled after saving, which seems normal.
Then I added an OpenSocial gadget to my Liferay page, pointing it to Jira’s activity stream URL. In the OAuth management section, I selected RSA_private authentication and used portal.mycompany.com as the consumer key.
However, the activity stream appears blank in Liferay. The server logs show this error:
jodd.bean.BeanException: Simple property not found: oAuthConsumerId Invalid property: 'OAuthConsumerImpl#oAuthconsumerId
What could be causing this issue? Should the consumer key match the Common Name from my certificate generation process? Any help would be appreciated.
This looks like a property mapping issue with your OAuth consumer setup. I’ve hit this same problem with Atlassian integrations before. The oAuthConsumerId error usually means Liferay’s handling the OAuth consumer object wrong internally. Check your OpenSocial gadget config in Liferay’s Control Panel first. The service name needs to match exactly what you set up in Jira’s Application Links. Also make sure your RSA private key file has the right permissions and Liferay can actually read it. Here’s what worked for me - delete the OAuth consumer entry in Liferay and create it fresh instead of editing the existing one. The internal mapping gets messed up sometimes during updates. And double-check that your Jira instance is reachable from the Liferay server with no firewall blocking the OAuth handshake.
i think ur right about the case sensitivity! also check if the consumer keys are matching exactly. sometimes jira and liferay can have issues with versions too, so make sure they’re compatible.
That BeanException usually happens when there’s a version mismatch between Liferay and your OpenSocial gadget. I ran into this same issue with Liferay 6.2 and newer Jira versions - the property name casing problem means your Liferay’s probably running an older OpenSocial library that expects different property names. First, check your Liferay version and make sure the OpenSocial gadget specs match what your portal actually supports. I had to downgrade my gadget XML from version 2.5 to 2.0 in the definition file to fix this. Also, don’t worry about the certificate Common Name matching the consumer key - they can be different in most setups. What really matters is that the consumer key is identical in both systems and your RSA keys are clean (no extra characters or line breaks).