Issue with New OAuth 2.0 App for Jira Integration in iFrame Application

gmoorthy_ggca5u

Hello guys,

 

We are currently experiencing an issue with a new OAuth 2.0 app integration for Jira while testing our application in a different environment. Below are the details of the problem, steps we followed, and the issue encountered:

Background:

We successfully use a Jira OAuth 2.0 app in our existing React + Node.js application to fetch Jira-related data for our organization's users. The integration works as expected. However, for testing our application in a new iFrame (Electron + Node.js) environment, we created a new OAuth 2.0 app with similar settings.

Steps Followed to Create the New OAuth App:

1. App Creation: Created a new app in the Atlassian Developer Console.
2. Enabled Sharing: Under the Distribution tab, we enabled the sharing option and provided the required terms of service and privacy policy.
3. Configured Permissions: Set up the required Jira scopes and granular scopes under the Permissions tab.
4. Authorization Settings: Configured the callback redirect URL under the Authorization tab.

Issue:

• When users try to authorize the new app within the iFrame (Electron + Node.js) environment:
  • The prompt screen appears correctly, allowing users to accept the grant request.
  • After clicking the "Accept" button, the authorization fails, and the app displays a "Something went wrong" error.
  • The authorization flow does not send the authorization code to the configured redirect URL.

This behavior is specific to the new environment, as the same configuration works seamlessly in the existing React + Node.js application.

Request for Assistance:

We suspect this issue might be related to:

• The iFrame/Electron setup interfering with Jira's OAuth 2.0 flow.
• Additional security or configuration requirements for the redirect URL when used in iFrame/Electron.
• Any recent changes in OAuth 2.0 handling for Jira apps.

We would greatly appreciate guidance or suggestions from the community or Atlassian team on resolving this issue. If there are any specific configurations or additional steps required for iFrame/Electron environments, please let us know.

Thank you in advance for your support!

Sahir Maharaj_28wu8p

Hello @gmoorthy

Based on my limited experience, the issue with OAuth 2.0 in your iFrame environment could be related to security restrictions. Jira OAuth flows often block iFrames due to modern browser security policies, which prevent embedding login flows for protection.

Try testing your integration in a non-iFrame environment to confirm if the iFrame setup is the issue.

Also, verify that the redirect URL used in your OAuth configuration is valid and accessible within your new environment.