Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

AuthenticationFailedException: AUTHENTICATE failed during test of OAuth2.0 Exchange connection

Damien Turner January 29, 2021

I followed the guide https://confluence.atlassian.com/jiracore/setting-up-oauth-2-0-integration-1005784173.html , but I can not find these scopes

https://outlook.office.com/IMAP.AccessAsUser.All or https://outlook.office.com/POP.AccessAsUser.All, and offline_access

I used the graph scopes in the Oauth 2.0 configuration and it tested successfully.  From what I read the scopes in the document are deprecated. 

Then I moved to the Incoming Mail configuration and during the test that is where I receive authentication failed. 

Any help is much appreciated !

1 answer

0 votes
Craig Shannon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 4, 2021

Hi Damien,

Thanks so much for your question.

Are you still unable to connect to your mailbox using OAuth 2.0? Are you trying to setup incoming emails for Jira or JSM? As you have already linked to the document on how to setup OAuth, I assume that you have follow the setup and added the three scopes which you mention in your question. 

If this is for JSM, I would suggest turning on additional logging to help understand what the issue that you are experiencing is. You can do this by enabling the System property `mail.debug` as described at the bottom of this document: https://confluence.atlassian.com/jirakb/enable-mail-debugging-mode-in-jira-server-816520648.html

I would also suggest turning on logging for debug logging for the package `com.atlassian.jira.internal.mail`, for details on how to do this, see https://confluence.atlassian.com/jirakb/change-logging-levels-in-jira-server-629178605.html

With this enabled, you should be able to see protocol level logging from the mail library so we will be able to see at which stage the authentication fails and also application logging to track down any info that we might get from there.

With this extra logging, hopefully we’ll be able to get a better idea on the specifics of the error that you are seeing and help you further.

Thank you,

Craig

Jira Service Management

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events