AppLinks を使用して Atlassian 製品にリンク

AppLinks is a bundled app that allows you to set up links, share information, and provide access to certain resources or functionality across multiple Atlassian products. We recommend using OAuth authentication for app links because of the greater security inherent with that protocol. We no longer recommend the Trusted Apps and Basic authentication types.

Linking Jira to other Atlassian products allows you to include information from those products directly in Jira projects and work items. For example, if you link Jira to Confluence, you can include shortcuts to Confluence page links when creating or editing a Jira work item. Linking Bitbucket Data Center and Jira allows you to view branches, commits and pull requests that correspond to your stories in Jira.

We recommend using apps to link Jira to products such as Salesforce or Zendesk. For products that don't have a supported Jira integration, you can create a custom app link.

はじめる前に

Cloud から Data Center インスタンスへのリンク

If you’re looking to integrate Atlassian Cloud and Data Center products that live in your network, you can avoid allowlisting incoming connections and IP ranges (required when linking from Cloud products) by using app tunnels. How to use app tunnels

複製されたサイトへのリンク

Creating an app link between a site and its clone (a Jira site exported from the source site and then imported onto a second site) isn’t supported. To work around this:

• いずれかのサイトが Jira Data Center の場合は Data Center ID を変更する

• Perform a cloud-to-cloud migration instead.

Create an app link

1. Jira 管理者権限を持つユーザーとして Jira にログインします。

2. Select Settings (), then Products. Select App Links in the left menu.

3. [リンクを作成] を選択します。

4. 次からリンクの種類を選択します。

   • Tunnelled app link: This link reuses an existing app tunnel to forward the traffic to your network. App tunnels can only be used to link to Atlassian Data Center products.

   • Direct app link: This link connects to Atlassian products or external apps directly. It needs to be able to reach them, which might require opening your network for incoming connections. When adding the Cloud URL, use the https://instance.atlassian.net. If the https:// is not used, the link will not be completed.

5. [続行] を選択して、接続の詳細を確認します。この画面に表示されるオプションをいくつか紹介します。

• [The data center have the same set of users... (データ センターに同じユーザーのセットがある...)] をオンにすると、このリンクは OAuth (偽装あり) 認証を使用して構成されます。

• If you are not an admin on both data centers you won't be able to set up a 2-way (reciprocal) app link. If you want to go ahead and create a 1-way link anyway, clear the I am an administrator on both instances checkbox.

6. Use the wizard to finish configuring the link. If the app you are linking to does not have the AppLinks plugin, you must supply additional information to set up a link with OAuth authentication.

When you complete the wizard, the AppLinks plugin will create the link between your apps using the most secure authentication method that is supported between the two apps. See the AppLinks User Guide for more information.

The new link will appear on the Configure AppLinks page, where you can:

• Edit the settings of the app link (for example, to change the authentication type of the link) using the Edit () icon.

• Specify the default instance if you have multiple links to the same type of app.

• ata centers) using the Make Primary link. See Making a primary link for links to the same app type for more information.

OAuth 認証

Atlassian's app links provide both OAuth and OAuth with impersonation authentication types:

OAuth 認証

OAuth authentication redirects a user to log in to the remote app, after which tokens generated on their behalf are used to authorize requests made from the local app. The remote app handling the request uses the access permissions of the account with which the user logged in on that remote app.

一般的なシナリオには以下が含まれます。

• You are setting up an app link between two apps that do not share the same set of users.

• You want to continue using a link to an app that now allows public sign-on and the link was previously configured with a shared userbase. You can update your app link by changing OAuth (impersonation) to OAuth when editing the app link.

See OAuth security for app links for more information.

偽装を伴う OAuth

Atlassian OAuth with impersonation makes it easy for your users to benefit from the deep integrations between Atlasssian apps:

• they're automatically authenticated on the other app and don't get asked to authorize requests.

• ユーザーには、自身が表示権限を持つ情報のみが表示されます。 

偽装認証は、現在ログイン中のユーザーに代わりリクエストを行います。

Note that Atlassian OAuth with impersonation can only be used for app links between Atlassian apps. Furthermore, it should only be used when the two apps share the same userbase, typically managed with an external directory using LDAP.

一般的なシナリオは以下のとおりです。

• You've set up an app link but your users still have to authenticate regularly. This can occur when the app link has been configured to not share the same userbase. If those apps do share the same user base, you can update your app link by selecting OAuth (impersonation) when editing the app link.

See OAuth security for app links for more information.

開発者ツールへのリンク

When you create a new app link between Jira and an instance of Bitbucket Data Center, Fisheye, Crucible or Bamboo, 2-legged (2LO) and 3-legged OAuth (3LO) are enabled by default. 2LO is required for information from any of those apps to be included in the summaries in the Development panel; 3LO is used to ensure that a user has authenticated with the other apps before they get to see the information in any of the details dialogs.

トラブルシューティング