Application Links 5.0 Documentation
アトラシアンのアプリケーション リンクでは 2 つの OAuth セキュリティ モデルを使用できます。
OAuth 認証 | 偽装を伴う OAuth | |
---|---|---|
説明 |
|
|
メリット |
|
|
要件 |
|
|
You shouldn't link to a non-Atlassian application using OAuth authentication, unless you trust the other application. Linked applications 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 always uses a pre-configured user, and not the logged-in user, when making a request. The server handling the request determines the level of access to use based on the access permissions of that pre-configured user, and this is used for requests from all users.
A typical scenario is setting up an application link between two applications that trust each other and that do not share the same set of users.
Newly created application links use OAuth by default and automatically enable both 3-legged OAuth and 2-legged OAuth.
Note that application links between Jira Software and Atlassian developer tools (Bitbucket Server, Bamboo, Crucible, Fisheye) must have Trusted Applications and Basic Access authentication disabled.
You may need to update an existing application link to use OAuth authentication when: When you update an older application link to use OAuth authentication, 3-legged authentication is applied by default, but you need to explicitly enable 2-legged OAuth. Here's how to do that in Jira Software, but the process is much the same for other Atlassian server products: The application link update process will log you into the linked application (such as Bamboo) for a short time to configure that end of the link, before returning you to Jira Software. 注意: 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. 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.
Atlassian OAuth with impersonation can only be used for application links between Atlassian applications. Furthermore, it should only be used when the two applications have the same userbase, typically managed with an external directory using LDAP.
Impersonating authentication makes requests on behalf of the user who is currently logged in. People will see only the information that they have permission to see.
一般的なシナリオには以下が含まれます。
Here's how to do that in Jira Software (the process is much the same for other Atlassian server products):
You can reset the OAuth authentication for an existing application link by disabling OAuth and then re-enabling it. You might need to do this when the OAuth consumer key has gone stale (you're seeing the consumer_key_unknown
error).