This documentation relates to an earlier version of Application Links.
View

Unknown macro: {spacejump}

or visit the current documentation home.

The instructions on this page describe how to update an existing application link, where the non-UAL remote application has been upgraded to a version that includes UAL (Unified Application Links).

When an application link is created between a UAL-enabled application and a remote legacy application (either a non-Atlassian product, or an older version of an Atlassian product that did not ship with UAL), this link is configured to run in "legacy mode". While there is no distinguishable difference to a user, connecting and configuring non-UAL application links is a little different. For example:

  • Setting up OAuth requires manual configuration by the administrator. In OAuth authentication for UAL-to-UAL links, exchange of the consumer keys and public keys is done automatically.
  • The Trusted Applications protocol (Atlassian-specific) will not be available for authentication.

If you upgrade your remote application to a version that does include UAL, the application link will continue to work. However, upgrading your link to "full UAL mode" may simplify link configuration and make additional authentication protocols available (as mentioned above).

On this page:

To upgrade your application link to "full-UAL mode":

  1. After you have upgraded your remote application to a version that includes UAL, navigate to the administration console of your local application. A warning will be displayed, requesting that you upgrade the link to full-UAL mode (see 'Upgrading an application link - Warning message' screenshot below).
  2. Click 'Upgrade' in the warning message to start the upgrade wizard.
  3. Complete the upgrade wizard to upgrade your link to full-UAL mode (see 'Upgrading an application link wizard' screenshot below). The wizard will be similar to the one used when you first added the link. Note the following:
    • You will be prompted to make your application link bidirectional. You will need to provide administrator credentials for your remote application, if you choose to do so.
    • If you make your application link bidirectional, you will also be able to make any entity links (for the application link) bidirectional. For example, you may be able to link your JIRA project to a FishEye repository and also make a reciprocal link.


Screenshot above: Upgrading an application link - Warning message


Screenshot above: Upgrading an application link wizard

Adding an Application Link
Configuring Authentication for an Application Link

  • No labels





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.