UCCX, O365 and OAuth2

[Clifford McGlamry]

Microsoft is ending support for basic authentication

https://blog.rebex.net/office365-imap-pop3-oauth-unattended

 https://devblogs.microsoft.com/microsoft365dev/end-of-support-for-basic-authentication-access-to-exchange-online-apis-for-office-365-customers/

So, how does one configure OAuth2 when using UCCX?  I don't see any way to do this, and I've seen nothing from Cisco on this either. 

[Roger Kallberg]

Maybe it would help if you were to outline what you’re using O365 for in relation to CCX? From the top of my head I cannot think of any use related to this.

[Clifford McGlamry]

EMail queuing with Social Miner (or whatever they are calling it this week).  Setting up the e mail server and queue options does not have an OAuth2 option.  

[Roger Kallberg]

Ah, I’ve never done such integration, so it didn’t come to mind. I’ll dig around and see what I can find. One question, is the solution as such under support by Cisco or has it gone past end of support?

[Clifford McGlamry]

It's under support, but this is not covered in any of the documentation, nor does the product appear to have the correct entry points to set up OAuth2.  

[david.macias]

I thought for now there was a way to re-enable basic auth for your tenant. https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-february-2021-update/ba-p/2111904

"We are building the capability to allow you to re-enable the protocols yourself via Support Central in the Microsoft 365 admin center. If you find yourself in this situation, you’ll be able to request help in the Microsoft 365 admin center, and we’ll allow you to re-enable these protocols until we disable them in the future."

I would 100% hammer on Cisco to figure out a COP file to get SocialMiner to work with oauth2.

david

[Clifford McGlamry]

Yes, you can re enable Basic Auth....but they are going to PERMANTENTLY DISABLE IT during the first part of December 2022.  At best, re enabling it is a temporary fix.  

[david.macias]

Anyone get an answer on this?

david

[Clifford McGlamry]

@david.macias , nope.  It's been crickets....

[bill.king1]

I apologize if I'm not following, but isn't this defect re: how to make it work with OAuth 2 what you want? It says it is resolved in release 12.5.1.11003.282?
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd10901

[david.macias]

This is excellent news. I'll ask one of my customers to upgrade to test it and report back.

david

[Clifford McGlamry]

@bill.king1 Thanks for that....HOWEVER, that release is not available on CCO.  I absolutely hate it when they do this.  This bug note says it was addressed back in October, but the fix isn't publicly available.  Frustrating!!!!

[david.macias]

@Clifford McGlamry I did some research on this and here's what I found (sent this to a customer): So Microsoft is forcing everyone with an email account to use OAuth for their authentication, you can no longer just have an username and password. And this type of authentication was NOT supported with UCCX. However, it looks like this has been fixed (https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd10901), but we need to be on 12.5.1.11003.282, which based on my notes we're not. How much of a pain will it be for you to upgrade the lab to this version? At a minimum we need to be on 12.5(1) SU2 ES03.

Check out the release notes and they do mention the bug id.

david

[Clifford McGlamry]

Actually in the process of spinning this up right now.  Thanks @david.macias 

[david.macias]

Excellent, please report back!

david