WF mailer and oAuTH2.0 and office365

classic Classic list List threaded Threaded
2 messages Options
kly
Reply | Threaded
Open this post in threaded view
|

WF mailer and oAuTH2.0 and office365

kly
Hello,

I see there is a thread already for 12.2, but at my work iwe're still on 12.1.3.

http://erman-arslan-s-oracle-forum.124.s1.nabble.com/WF-mailer-and-oAuTH2-0-and-office365-td8771.html

Microsoft has already delivered support for Client Credential Flow for IMAP.

https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=70577

Can anyone share any workaround if Oracle doesn't deliver any solution for 12.1.3?

Reply | Threaded
Open this post in threaded view
|

Re: WF mailer and oAuTH2.0 and office365

ErmanArslansOracleBlog
Administrator
This post was updated on .
Hi Kly,

Facts:
-----------------
October 1, 2022 -- Microsoft will begin to permanently disable basic authentication.
This will impact EBS customers using Microsoft's Office 365 Exchange Online.
Microsoft will; urn off Basic Authentication in Exchange Online for Exchange ActiveSync (EAS), POP, IMAP
and Microsoft will onnly use Modern Authentication (OAuth 2.0 token based auth) and this is done for security concerns..

*Please see -> https://blogs.oracle.com/ebstech/post/support-for-oauth20-with-ebs-workflow-notification-mailer

-They say -> We understand the criticality of this requirement and the tight timeline between June 2022 and October 2022.

*Also see -> EBS Workflow Mailer Configuration with OAuth 2.0 Token-Based Authentication for Cloud-Based Email Services (Gmail, Yahoo, Office365, etc) (Doc ID 2650084.1)

*Development is in progress with -> Enhancement Request  Bug 30505419 - 30840012 - WORKFLOW MAILER SUPPORT OF OAUTH2 - OFFICE 365 PLATFORM

-What they say is ; "Any solution will first be delivered on top of the new 12.2.x techstack.
It is unclear at this time if EBS 12.1.3 WF Mailer would be able to be adapted for this change considering EBS Release 12.1.3 is in Sustaining Support since Jan 1, 2022
and uses an older technology for its techstack which might not be able to handle OAuth 2.0 authentication."

So I can't give you a %100 sure answer for your question.. We will see.. You may still try your chance and ask it to Oracle....