Once you have proceeded through the prompts you can click on Connect and Download to save the credentials. Please contact or check online on how to change permissions to do so. If you received any errors at this stage, it likely means that the admin has not given this program permissions to access the specific scopes that are being requested (eg. The screenshot below captures what this popup will look like…
If you received the error the Autodiscover service couldn’t be located, please check this KB article for possible ways to mitigate this. That will work provided your admin has configured support for this new form of authentication. Note that you need to be on v3.2 build 1048 for this to work properly.
Need to move away from Basic Auth? If you are trying to move away from Basic authentication or are trying to force the program to not use it, we suggest you enter the wrong password and if you try to test the connection after that, it should popup the ability to use the second factor auth. Basic authentication fails to work (tries basic by default always).The program currently triggers this popup only if the following are met: Shown below is an example of a popup using Microsoft authentication.
This new build now includes support for modern authentication for these types of mail servers: To cater to this, v3.2 build 1049 introduces full support for Microsoft based second factor authentication (OAuth) and Google’s second factor authentication OAuth for cloud-based or hybrid environments. This applies to both Office 365, Exchange and Google, GSuite accounts. Google had a similar announcement earlier. None currently, if one should become available this will be updated to reflect that state.Microsoft last year announced that basic authentication will be discontinued in their products starting October 2020. It seems that the ProPlus accounts might still permit this after the set date, however it seems clear that improving security is the goal of this forced change, and perhaps it would benefit Jira to follow suit. Without this feature, regular office 365 accounts won't permit applications like Jira to connect to them. Implement some other method of allowing Jira to authenticate to an office 365 mailbox, such as OAuth2. More details about the upcoming changes to Microsoft's products can be found in Suggested Solution As of today, basic auth (username and password) via IMAP/POP is the only way to make Jira able to use an Office 365 mailbox for receiving email. Office 365 is planning to discontinue support for basic auth on services like POP and IMAP on October 13, 2020. The rollout should take a day or two to propagate to all tenants. We would like to announce the rollout of the Microsoft OAuth for Incoming Emails’ on Jira Software Cloud.
0 kommentar(er)
