We've Jira (8.20) and Bitbucket (7.17) (both DC Edition). Application links are working and connectivity is well. Application link via OAuth (Im) at both end.
Issues:
* While viewing Development tools in the JIra project - get below error:
Authentication Warning
Applications flagged with can get access to more features if two-legged authentication (2LO) is enabled on their application links. Follow these instructions for enabling 2LO.
* Configure option in the Application Link isn't available hence can't make any changes to the Outgoing/Incoming Authentication.
The link works for me, but here is the content:
When you connect Atlassian applications using application links you get the security of the industry-standard OAuth authorization protocol. For a great introduction to how the OAuth authorization flow works, see this blog post.
To update an application link to use just OAuth, see Update application links to use OAuth.
If you want to create an application link between two Atlassian applications, see Link Atlassian applications to work together.
For version 5.2 and later, application links no longer support the Trusted Applications or Basic Access authentication types.
There are two OAuth security models that you can use with Atlassian application links:
OAuth authentication |
OAuth with impersonation |
|
---|---|---|
Description |
|
|
Benefits |
|
|
Requirements |
|
|
You shouldn't link to a non-Atlassian application using OAuth authentication, unless you trust the other application. Applications connected using application links have the ability to use OAuth to impersonate users and so are a potential security risk for the applications they connect to. If your server is compromised, the data there and on linked servers is at risk.
OAuth authentication redirects a user to log in to the remote application, after which tokens generated on their behalf are used to authorize requests made from the local application. The remote application handling the request uses the access permissions of the account with which the user logged in on that remote application.
Typical scenarios include:
See Update an existing link on this page for instructions.
Atlassian OAuth with impersonation makes it easy for your users to benefit from the deep integrations between Atlasssian applications:
Impersonating authentication makes requests on behalf of the user who is currently logged in.
Note that Atlassian OAuth with impersonation can only be used for application links between Atlassian applications. Furthermore, it should only be used when the two applications share the same userbase, typically managed with an external directory using LDAP.
A typical scenario is:
See Update an existing link on this page for instructions.
You may need to update an existing application link to use OAuth authentication when:
Here's how to do that in Jira Software, but the process is much the same for other Atlassian server products:
Go to the 'Configure Application Links' page in the admin area of the local application.
You may see a DEPRECATED lozenge beside links that need to be updated.
In the 'Edit' dialog, set the local authentication for the link under 'Connections':
Choose either:
Make sure that that the authentication matches for the local and remote ends of both the incoming and outgoing directions.
Click Save changes.
Go to the 'Configure Application Links' page in the admin area of the remote application. Choose the instructions column here that matches the UI you see (they both achieve the same result):
In the 'Edit' dialog, set the local authentication for the link under 'Connections':
Choose either:
Make sure that that the authentication matches for the local and remote ends of both the incoming and outgoing directions.
Click Save changes.
In the 'Configure' dialog, click Outgoing Authentication and then the OAuth tab:
Now, select Enable 2-Legged OAuth, assuming that the applications have different userbases.
Optionally, select Enable 2-Legged OAuth with impersonation, if both applications share the same userbase, typically managed with an external directory using LDAP.
Click Update.
Now, click Incoming Authentication and then the OAuth tab:
Now, select Enable 2-Legged OAuth, assuming that the applications have different userbases.
Optionally, select Enable 2-Legged OAuth with impersonation, if both applications share the same userbase.
Click Update.
Note that:
Users who can see summarized data in the Jira Software Development panel may not have permission to see all the information that contributed to those summaries and that is visible in the details dialogs (for example, for branches, commits and pull requests). That is, the details dialogs respect the access permissions that users have in the connected applications.
Your team members must have the 'View Development Tools' permission in Jira Software to see the Development panel for an issue.
Application links between Jira Software and Atlassian developer tools (Bitbucket Server, Bamboo, Crucible, Fisheye) must have Trusted Applications and Basic Access authentication disabled.
If you run an application on port 443, you must use a valid SSL certificate (which is not self-signed) to get the full functionality available.
Hi,
Anyhow issue is solved due to another bug case. But in the answer "Click Edit for the application link you are updating." this doesn't available anymore.
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.