OAuth support for Unified Messaging

[hans.choi]

I see this document for Collaboration applications.

https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/jabber/11_9/Unified-CM-OAuth-Whitepaper-v17-FINAL.pdf

However, it does not mentioned the Unified Messaging service account.

We are in the process of transitioning all of our users away from using legacy authentication methods – including POP/IMAP/SMTP.

Microsoft is actually deprecating support for legacy authentication in October 2020:  https://support.microsoft.com/en-us/help/4521831/exchange-online-deprecating-basic-auth - so it will break for all of your clients’ unified messaging/O365 integration at that time, if they aren’t switched to using modern authentication libraries.

Any plan to support OAuth for Unified Messaging instead of Basic/NTLM?

Kenny

[Jaime Valencia]

Roadmap questions are NDA and cannot be discussed in public forums, if you're a partner, you can try the partner forum or your SE.

[piyush aghera]

Not sure if you have already resolved this issue but it is possible to use OAuth 2.0 with Cisco Unity Connection to configure unified messaging:

Here are the steps in summary:

1. Verify Unity Connection for OAuth support
2. Service Account in AD/Office365
3. Register an application in Microsoft Azure
4. Configure CUC Unified messaging for OAuth 2.0

Please refer my blog below for steps in detail:  https://voiptechwikis.com/unified-messaging-oauth/

Thanks.