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).