-
Close Search
Newbie
7 posts
Please review the ability for Coldfusion to utilize Modern Authentication (OAuth) when connecting to Microsoft Exchange Online vs Basic Authentication (Presently Using Exchange Web Services).
Microsoft is disabling Basic Authentication October of 2022 and we would like to migrate anything using it to Modern Authentication.
https://techcommunity.microsoft.com/t5/exchange-team-blog/basic-authentication-and-exchange-online-september-2021-update/ba-p/2772210
Please let me know what would be involved in order to achieve this?
Has anyone seen this from Microsoft?
What does this mean for cfexchangeconnection tag?
Has anyone seen this from Microsoft?
What does this mean for cfexchangeconnection tag?
You must be logged in to post a comment.
- Most Recent
- Most Relevant
To migrate ColdFusion from Basic to Modern Authentication (OAuth) with Exchange Online:
- Register your app in Azure AD for OAuth credentials.
- Update the cfexchangeconnection tag to use OAuth tokens.
- Implement logic to acquire and refresh OAuth tokens.
- Ensure proper permissions and thoroughly test the integration.
- Odoo-Power BI
Check Microsoft’s documentation for updates on cfexchangeconnection support.
https://www.cdata.com/kb/tech/office365-jdbc-coldfusion-query.rst
I found an article. Third party though
I’ve added this as a Feature Request in the Adobe Tracker. Go vote for it!
Adobe is finally working on this. They are moving our ticket to beta.
I was thinking this would have been addressed with the focus of CF2021 being on cloud computing but, obviously not. Hoping that Adobe has an update, or replacement, for <cfexchangeconnection> in the works for an update in the coming months?
I recently migrated a Java application from using Basic Authentication for IMAP access to Outlook to use OAuth2 and JavaMail. It was a fair bit of work. These are the docs I used to solve it. Essentially I had to create a custom API Application in Azure Portal, then manually generate a Auth Code. With the Auth Code I could programatically retrieve the access_token, which has a short lived TTL. Using the access_token you can generate a refresh_token, then the refresh_token has a very long TTL. When the access_token expires (hourly), use the refresh_token to get a new one programatically. Manual intervention is only needed when either the initial Auth Code or refresh_token expires .
https://docs.microsoft.com/en-us/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth
https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-configure-app-access-web-apis
