Why can't I connect to Microsoft with oAuth2.0 setup?

Paul Roberts_i4orgc

Hi,

Our software has been down since Microsoft turned off basic authentication recently.  We can no longer create tickets through e-mail.

We noticed that the latest version had something other than basic Authentication.  OAuth2.0.  So we updated to 8.13.1.

Working with the e-mail team we were able to complete the oAuth2.0 setup details in Jira on the Microsoft side.  However, when we go to test it just does a loop.

After clicking the test we login with the user and password and we receive a pop-up that says someone with admin rights needs to login.  We have an O365 admin login and confirm the pop-up that allows the app.  Then it reloads the Jira screen.  At this point we can do the test link again and the same thing happens.  Login/Admin Login/Allow.  It just does this loop.

Question.  There is that "redirect URL" we have registered that points to our server.  In order to complete this authentication process does Microsoft actually need to make a connection back to our server using that URL?  That wouldn't work because the DNS doesn't resolve externally and because it is not a public server.

That is the main question.  Should this process be able to be setup if our Jira server is not setup to be accessed from the Internet?  If yes, where would I find the logs containing the most accurate error messages for this process.  If no, is there another way to login to O365 so we can retrieve our IMAP e-mails and have the cases created?

Any ideas would be greatly appreciated as we are basically down.

Thanks!

Artur Moura

Hi Paul,

Just for us to stay on the same page, are you followed the below steps?

1. 1. Log in as a user with the JIRA System Administrators global permission.
   2. Navigate to Administration > System > OAuth 2.0
   3. Click on Add new integration
   4. At the "Service provider", select Microsoft
   5. Click on Copy at the Redirect URL field
   6. Let's login to "https://portal.azure.com/"
   7. Click on App registrations
   8. Click on New registration
   9. Let's pickup a friendly name so it will be easier to identify
   10. Under the "Supported account types" section, let's choose "Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)"
   11. Under the "Redirect URI" section, let's pickup Web and insert the URL from step #5 above
   12. Click on Register
   13. Click on API permissions
   14. Click on Add a permission
   15. Click on Microsoft Graph
   16. Select Delegated permissions
   17. Let's select the following permissions:

       OpenId permissions: offline_access
       IMAP: IMAP.AccessAsUser.All
       POP: POP.AccessAsUser.All
       

   18. Click on Add permissions
   19. Click on Grant admin consent for ...
   20. Click on Certificates & secrets
   21. Click on New client secret
   22. Choose a description and expiration date
   23. Take note of the Value generated (this will be used as the "Client secret" at Jira)
   24. Click on Overview
   25. Take note of the Application (client) ID (this will be used as the "Client ID" at Jira)
   26. Let's go back to Jira and complete the configuration by inserting the following details:
       1. Client ID (from step #25 above)
       2. Client secret (from step #23 above)
       3. Scopes: "https://outlook.office.com/IMAP.AccessAsUser.All", "https://outlook.office.com/POP.AccessAsUser.All" and "offline_access"
   27. Click on Save
   28. Test the connection
       If the connection was successful, please proceed
   29. Navigate to Administration > System > Incoming Mail
   30. Click on Add mail server
   31. At the "Service Provider" field, let's pick up Microsoft Exchange Online / Outlook (IMAP)
   32. At the "Username" field, insert the email address being used by Jira
   33. At the "Authentication method" field, select the new server created under the OAuth 2.0 menu
   34. Click on Authorize
   35. Click on Test Connection
   36. Click on Save

Cheers,

Artur