EWS - Basic Authentication Retirement

[Gajack33]

Hi Collie147,

I think this application will not work anymore beginning 13 October because they retire basic authentication for EWS and this is what we use in this app...

As previously communicated in MC191153, beginning October 13, 2020, we will retire Basic Authentication for EWS, EAS, IMAP, POP and RPS to access Exchange Online. Note: this change does not impact SMTP AUTH.

There are several actions that you and/or your users can take to avoid service disruptions on client applications, and we describe them below and in the blog. If no action is taken, client applications using Basic Authentication for EWS may be unable to connect after October 13, 2020.

Any application using OAuth 2.0 and connecting using any of these protocols, will continue to work without change or interruption.

[What do I need to do to prepare for this change?]

You have several options on how to prepare for the retirement of Basic Authentication.

• You can start updating the client applications your users are using to versions that support OAuth 2.0 today. For mobile device access, there are several email apps available that support Modern Authentication, but we recommend switching to the Outlook app for iOS and Android as we believe it provides the best overall experience for your M365 connected users. For desktop/laptop access, we encourage the use of the latest versions of Outlook for Windows and Outlook for Mac. All Outlook versions including, or newer than, Outlook 2013 fully support OAuth 2.0. • If you have written your own code using these protocols, you will need to update your code to use OAuth 2.0 instead of Basic Authentication, you can reach out to us on stack overflow with the tag exchange-basicauth if you need some help. • If you or your users are using a 3rd party application, which uses these protocols, you will either need to: • reach out to the 3rd party app developer who supplied this application to update it to support OAuth 2.0 authentication

[Collie147]

Hi Collie147,

I think this application will not work anymore beginning 13 October because they retire basic authentication for EWS and this is what we use in this app...

As previously communicated in MC191153, beginning October 13, 2020, we will retire Basic Authentication for EWS, EAS, IMAP, POP and RPS to access Exchange Online. Note: this change does not impact SMTP AUTH. There are several actions that you and/or your users can take to avoid service disruptions on client applications, and we describe them below and in the blog. If no action is taken, client applications using Basic Authentication for EWS may be unable to connect after October 13, 2020. Any application using OAuth 2.0 and connecting using any of these protocols, will continue to work without change or interruption. [What do I need to do to prepare for this change?] You have several options on how to prepare for the retirement of Basic Authentication. • You can start updating the client applications your users are using to versions that support OAuth 2.0 today. For mobile device access, there are several email apps available that support Modern Authentication, but we recommend switching to the Outlook app for iOS and Android as we believe it provides the best overall experience for your M365 connected users. For desktop/laptop access, we encourage the use of the latest versions of Outlook for Windows and Outlook for Mac. All Outlook versions including, or newer than, Outlook 2013 fully support OAuth 2.0. • If you have written your own code using these protocols, you will need to update your code to use OAuth 2.0 instead of Basic Authentication, you can reach out to us on stack overflow with the tag exchange-basicauth if you need some help. • If you or your users are using a 3rd party application, which uses these protocols, you will either need to: • reach out to the 3rd party app developer who supplied this application to update it to support OAuth 2.0 authentication

Thanks for letting me know. Unfortunately I haven't been working any further on developing because nobody wants to meet in a meeting room any more! Thanks Teams and Zoom! Maybe when Covid is no longer a pandemic I might revisit this and apply any necessary updates. Appreciate the heads up.

[tomaskovacik]

https://github.com/probits-as/MeetEasier/

[tomaskovacik]

I merged your and probits-as fork: https://github.com/tomaskovacik/MeetEasier and it works in basic mode (no edit button work was done, so this must be fixed) yeh and MSAL.md file contains super simple howto regarding azuread config

[Collie147]

Brilliant. Best of luck with it, I haven't touched it in 3 years. But if there's something I can help with let me know (I might need to dive into it to jog my memory).

On Mon, 25 Jul 2022 at 14:09, Tomáš Kováčik @.***> wrote:

I merged your and probits-as fork: https://github.com/tomaskovacik/MeetEasier ad it works in basic mode (no edit button works was done, so this must be fixed)

[image: image] https://user-images.githubusercontent.com/4346464/180784628-c88cbd15-5c62-4cc9-95a1-ea8d4784590f.png

[image: image] https://user-images.githubusercontent.com/4346464/180784833-0c41e01d-13c1-476a-9851-cadfc2e9d8c0.png

— Reply to this email directly, view it on GitHub https://github.com/Collie147/MeetEasier/issues/3#issuecomment-1194026609, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADCHSGBUOSGJXQQVMZTN27DVV2GW5ANCNFSM4LE3ZBVA . You are receiving this because you commented.Message ID: @.***>

[tomaskovacik]

only porting calls to MS graph needs to be done for buttons functionality to work, but I am lost in that API :D it is completely different from EWS implementation

[TMA84]

Hi tomaskovacik,

can you help me with the settings for the graph api? Which settings have to be entered in the .env file and which settings in Azure AD?

[tomaskovacik]

https://github.com/tomaskovacik/MeetEasier/blob/master/MSAL.md

[tomaskovacik]

or check here https://github.com/probits-as/MeetEasier/commit/72c9bdbbebaed5a54a56a8b9f92d8d7ffbdb9193#commitcomment-86755485

[TMA84]

Hi, Iused your MSAL.md but I get following error:

Oops, there seems to be an issue with the credentials you have supplied. Make sure you typed them correctly and that you have access to Exchange Roomlists.

[tomaskovacik]

did you grant admin consent? try it

[TMA84]

thx for help I find the failure. My value for SEARCH_USE_GRAPHAPI was wrong.

[kaktuseek]

Is there anyone who wrote the roombooking.js for the msgraph and can you share it? For now i disabled the function, but it was good feature to book/extend/end meeting directly from the screen. Many thanks