OAuth 2.0 と Jira/Service Management の受信メール ハンドラーの統合に関連する一般的な問題のトラブルシューティング
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
Since Jira 8.10.0 (or in Service Management 4.10.0), it is possible to configure Jira or Service Management incoming Mail Handlers using the Oauth 2.0 integration instead of the Basic Authentication which will be eventually deprecated by Google and Microsoft.
Setting up a mail handler with the Oauth 2.0 authentication consists of 2 main steps which are explained in details in the documentation Integrating with OAuth 2.0 (for Jira 8.10.x-8.21.x) and Configure an outgoing link (for Jira 8.22.x+):
- 1st Step - Configuring an Oauth 2.0 integration
- Via the the page ⚙ > System > Oauth 2.0 for Jira 8.10.x-8.21.x
- Via the page ⚙ > System > Application links for Jira 8.22.x+
- 2nd Step - Configuring a Mail Handler
- Via the page ⚙ > System > Incoming Mail, in case of a Jira Mail Handler
- Via the page in Project Settings > Email Requests, in case of Jira Service Management (JSM) Mail Handler
Note that, if you are using either Microsoft US Government DoD or US Government GCC High account account, the configuration is slightly different than for other types of Microsoft accounts. This configuration is explained in the article How to configure a Microsoft US DoD or GCC High account with a Jira or a Service Management mail handler using Oauth 2.0.
We have identified 3 main categories of issues you might run into while configuring this Mail Handlers with the Oauth 2.0 authentication. Each of these issue has a dedicated KB article (mentioned in the table below) which explains how to troubleshoot and resolve them.
Most common types of Oauth 2.0 issues and their relevant knowledge base articles and bug tickets
Type of issue | KB article |
---|---|
Failure to open/view the Oauth 2.0 page | Link to the article |
Failure to configure an Oauth 2.0 integration (connection test failure) | Link to the article |
Failure to configure a Jira or JSM mail handler (authorization or connection test failure) | Link to the article |
Failure to fetch emails from GMAIL server (usually happens some time after successfully configuring it with Oauth 2.0) | Link to the article |
Failure to fetch emails from any type of mail server (usually happens some time after successfully configuring it with Oauth 2.0) | Link to the bug ticket |
アトラシアン サポートにデータを提供する
If none of the KB article listed above helped resolve the Oauth 2.0 issue you are facing, please make sure that you followed all the steps mentioned:
- in the documentation Integrating with OAuth 2.0 (Jira 8.10.x-8.21.x) or in the documentation Configure an outgoing link (Jira 8.22.x+)
- and in the community discussion Why can't I connect to Microsoft with oAuth2.0 setup (in case you are using Microsoft Office 365/Exchange)
You can also reach out to Atlassian Support via this link. To help the Atlassian support team investigate the issue faster, you can follow the steps below and attach all the collected data to the support ticket raised with Atlassian: