Microsoft Modern Authentication with Coldfusion

[talhaa4861378]

Microsoft is deprecating Basic Authentication:

https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic...

We have an Application built in Coldfusion which uses CFMAIL and CFEXCHANGECONNECTION to connect to Exchange online to send email and retrieve mail from mailboxes. I wanted to know how to make this work with Microsoft modern authentication which uses OAuth 2.0 token-based authorization. Any help regarding this will be much appreciated.

[talhaa4861378]

Following is a small code used in our application to fetch messages:

<cfexchangeConnection
action="open"
username ="#_username#"
password="#_password#"
server="#_server#"
protocol="https"
connection="testconn1"
serverversion="2016">

<cfexchangemail action="get" folder="Inbox" name="qGetMessages" connection="testconn1">
<cfexchangefilter name="maxRows" value="#num_of_record#">
</cfexchangemail>

Here username and password are the exchange online users and their respective passwords. I wanted to know how this will need to modified to work with modern authentication

[TBoons]

Have you been able to find out anything about this? The deadline is approaching. 

[cheryln97715160]

Anyone have any updates on this? Does not look like Adobe has fixed this issue yet?

[Charlie Arehart]

No fix YET, but one is due to be coming, before the end of the year. More on that in a moment.

You should vote for and then follow the tracker ticket CF-4212511 . There you will see not only how this has been begged for for over a year, with many comments since then. But see espeically comments from last month, first where I shared how Adobe's CF support folks had reported to me a couple of weeks ago that they are working on it "as a priority".

Then see Steve K reporting that he'd found a discussion in the CFML Slack where Mark Takata of Adobe said that "Our roadmap for providing the solution sees it shipping out to affected customers as a custom patch in December."

He also offered there, "Please post here if you are encountering this issue (i.e. you use cfexchange) so I can be sure we get you the patch."

So there's "an update" on this, for what it's worth.

[Charlie Arehart]

It is perhaps unfortunate that there are these (at least) 3 places where discussions about this are taking place (here, the tracker ticket, and Slack), but that can happen on any topic.

It's perhaps more unfortunate (in the minds of some) that Adobe (via Mark) may seem most active on Slack--where some people do not participate, or can't regularly, or won't (if they feel it's soo much to keep up on).

One can at least try to search there. First, I'll note that a recent initiative got that CFML Slack posted in a way (via the service linen.dev) which was supposed to make the channel searchable by Google and other engines. But I searched for that quote phrase above (in google) and got nothing.

If instead one searches for it at the front page of that linen.dev site that archives the CFML slack, https://cfml.linen.dev/, that at least DOES find the discussion. So that's at least an alternative way to search that slack channel...but it's not as good as Google finding it via that linen.dev service, which is how it was supposed to work.

Just kvetching.

[cheryln97715160]

Thanks for the update Charlie. I am on that ticket and did vote as soon as I found it yesterday (before posting here). I tried to access the Slack, but was unable to. It kept telling me the code it emailed me was invalid even though it wasn't, so I just gave up after trying multiple times and getting five codes. The Slack sounds like it is much more up to date than the tracker ticket, so it is unfortunate that not everyone can access the Slack channel easily. I will try the linen.dev search like you suggested. Glad to hear they hope to have fix out soon. Thanks!

[TBoons]

I changed my tune on this from "Hey Adobe Fix This!" to I will control the app. This is not Adobe dropping the ball, Microsoft moved the goal posts, which they have every right to do. Adobe also doesn't have to fall in line with Microsoft. I took the approach to rewite the app in Graph as to not rely on Adobe to fix the issue before it's too late. I feel that putting your hope that a good and complete rewrite by Adobe will be ready before the deadline is not a good stratagy.