Exchange connection with new OAuth 2.0 feature: "AuthenticationFailedException: AUTHENTICATE failed"

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問



プラットフォームについて: 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 は除く




問題

The log may include the following stack trace when setting up the incoming mail server :

The following appears in the Atlassian-Jira-incoming-mail.log

2020-11-25 07:12:23,082+0000 ERROR: Messaging Exception in service 'com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl' when getting mail: C3 BAD User is authenticated but not connected.
javax.mail.MessagingException: C3 BAD User is authenticated but not connected.


原因

This error is received when a user with which you are trying to configure the incoming mail server does not have the correct permission

ソリューション

  • configured the Oauth2.0 in Jira with the user using which you have generated the OAuth token will help in resolving the issue . 






最終更新日: 2020 年 12 月 28 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.