Microsoft have announced that they will be removing support for basic authentication for Office365 email services from in the second half of 2021. See https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-april-2020-update/ba-p/1275508 What is BMC's position regarding this change and how will it be addressed.? February 2021 Update Microsoft defer the removal of basic authentication for existing customers for at least 12 months. https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-february-2021-update/ba-p/2111904 |
Support for OAuth 2.0 in the Email Engine for the Exchange Web Services (EWS) protocol was introduced in Remedy AR System Server 20.02 patch 1. For customers that are unable to upgrade, OAuth 2.0 has also been tested and validated with the following Remedy releases using the workaround detailed below. - 19.08 - 19.02.001 - 18.08.001 - 18.05.005 - 9.1.04.002 - 9.1.03.001 Connect to the BMC ftp site and download the contents of the ftp://ftp.bmc.com/pub/ARRecommendedFixes/Server/OAUTH2/ directory which provide all the files necessary to run the 20.02.002 Email Engine on your older environment, a readme detailing the installation steps, and a document describing how to use the email test utility included in the update. *** The files included in the fix are 64 bit and require a 64 bit version of Java to work, if you require 32 bit versions, please contact support *** If you encounter problems or have questions regarding this workaround please open a case with BMC or your Remedy support provider. Additional information Registering Remedy Email Engine with Microsoft Azure for OAuth 2.0 authentication Remedy - Email Engine - Steps to register Email Engine with MS Azure for OAuth 2.0 authentication Remedy - Email Engine - FAQ when configuring Microsoft Azure for OAuth 2.0 authentication |