Exchange connection with new OAuth 2.0 feature: "AuthenticationFailedException: AUTHENTICATE failed"
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
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.
*Except Fisheye and Crucible
Problem
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.
Cause
This error is received when a user with which you are trying to configure the incoming mail server does not have the correct permission
Resolution
- configured the Oauth2.0 in Jira with the user using which you have generated the OAuth token will help in resolving the issue .
Last modified on Dec 28, 2020
Powered by Confluence and Scroll Viewport.