Upgrading an Application Link

Upgrading an Application Link (Local App Upgraded to Include Application Links)

When you upgrade from a Crucible version that does not include Application Links to a version that does, you will have the option of converting any Trusted Applications or OAuth links to Application Links. The advantage of converting your links to Application Links is that link configuration will be simplified in future.

To upgrade an application link when Crucible has been upgraded to include Application Links:

1. After your Crucible upgrade, go to the administration console.
2. Click 'Application Links'. The 'Configure Application Links' screen will show the following message:
   "There are existing Trusted Applications or OAuth relationships that should be upgraded to Application Links. Click here to upgrade."
3. Click the 'Click here to upgrade' link. The 'Existing Trust Relationships' screen will appear, showing all Trusted Applications and OAuth relationships that can be upgraded to Application Links.
4. Click the 'Upgrade to Application Link' link next to the desired trust relationship. The 'Upgrade to Application Link' wizard will appear.
5. Complete the wizard. The process will be similar to adding a new link (described on Adding an application link), except that most fields should be pre-filled.

Step 1	Step 2	Step 3	Step 4

Screenshots above: Upgrading an application link for your local application

Upgrading an Application Link (Remote App Upgraded to Include Application Links)

When an application link is created between a version of Crucible that supports Application Links, and a remote application that does not (either a non-Atlassian product, or an older version of an Atlassian product that did not ship with Application Links), this link is configured to run in 'legacy mode'. While there is no distinguishable difference to a user, connection and configuration without Application Links is a little different. For example:

• Setting up OAuth requires manual configuration by the administrator. If your applications support Application 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 support Application Links, the application link will continue to work. Upgrading your link may simplify link configuration and make additional authentication protocols available (as mentioned above).

To upgrade an application link when your remote application has been upgraded to include Application Links:

1. After you have upgraded your remote application to a version that includes Application Links, go to the administration console of your local application. A warning will be displayed, requesting that you upgrade the link to full Application Links mode.
2. Click 'Upgrade' in the warning message to start the upgrade wizard. Note the following:
   • You will be prompted to make your application link a reciprocal link. You will need to provide administrator credentials for your remote application, if you choose to do so.
   • If you make your application link a reciprocal link, you will also be able to make reciprocal links for your project links. For example, you may be able to link your JIRA project to a FishEye repository and also make a link from your FishEye repository back to the JIRA project.

Screenshot above: Upgrading an application link for remote application

Screenshot above: Upgrading an application link wizard

Related Topics

Adding an application link
Configuring Authentication for an Application Link