[cisco-voip] OAuth for Unity Connection/Office 365

Matthew Loraditch MLoraditch at heliontechnologies.com
Fri Jul 17 13:40:16 EDT 2020


Oh god, I never replied to this in April.

I posted here what I did that made things work:
https://community.cisco.com/t5/collaboration-applications/oauth-for-office-365-unity-connection-12-5-su2/m-p/4098350#M43230


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: Anthony Holloway <avholloway+cisco-voip at gmail.com>
Sent: Friday, July 17, 2020 12:14 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com>
Cc: Dave Goodwin <dave.goodwin at december.net>; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] OAuth for Unity Connection/Office 365

[EXTERNAL]

Looks like CUCM 11.5 SU8 addresses oauth with o365.  Did you see that?

On Wed, Apr 22, 2020 at 3:02 PM Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway%2Bcisco-voip at gmail.com>> wrote:
Matthew, What did you end up learning on this effort?

On Tue, Feb 4, 2020 at 10:10 AM Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
I did see that this morning and it fueled my confusion as it’s not needed (or useful) when using oauth and the EWS APIs.

They added OAuth because Microsoft is disabling the basic authentication that the Autodiscover and the old method used to use.

Really just hoping to get some insight from someone and hope to hear it’s half baked and will be finished later and/or I found an issue and it’ll get fixed. Will work with TAC eventually if I don’t get any feedback


Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
[cid:image005.jpg at 01D65C3F.CC179180]

From: Dave Goodwin <dave.goodwin at december.net<mailto:dave.goodwin at december.net>>
Sent: Tuesday, February 4, 2020 10:32 AM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] OAuth for Unity Connection/Office 365

[EXTERNAL]

Matthew, yes it is pretty new, and I have no setup with which to experiment or test, but have you read this section of the CUC 12.x doc? It seems to indicate CUC will still use Auto Discovery and in Step 6 it shows how to enable that in O365.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/12x/unified_messaging/b_12xcucumgx/b_12xcucumgx_chapter_01.html#ID-2370-000005f5

On Tue, Feb 4, 2020 at 10:04 AM Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:
This just came out yesterday so this is more directed for anyone lurking at Cisco, but how is this supposed to work?

Our UM has been disabled for months because of MS security requirements for resellers that broke the old way so I quickly installed this in my test lab to see if it will fix my issue.

According to all the MS documentation there should be no need to use the old Autodiscover, etc that Unity was using. You just connect to the default outlook.office365.com<http://outlook.office365.com> EWS url and use your oauth info and boom.

However, the fields for the old account are still there and mandatory and all the test options are going through and failing Autodiscover…

If I look at the Mailbox Sync Logs I don’t see any evidence it’s trying to use Oauth/EWS.

Going down the rabbit hole so everyone else doesn’t have to!












Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
[cid:image005.jpg at 01D65C3F.CC179180]
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 9409 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 431 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 561 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 444 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 19523 bytes
Desc: image005.jpg
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 6884 bytes
Desc: image006.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image720526.png
Type: image/png
Size: 9409 bytes
Desc: image720526.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image243340.png
Type: image/png
Size: 431 bytes
Desc: image243340.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image897390.png
Type: image/png
Size: 561 bytes
Desc: image897390.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image525745.png
Type: image/png
Size: 444 bytes
Desc: image525745.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200717/baf42205/attachment-0008.png>


More information about the cisco-voip mailing list