Getting started with oAuth2
wgermann at PACIFIC.EDU
Mon Oct 17 23:26:09 UTC 2022
I am working on the same thing for the same reason. I would also like any information on this.
From: omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> On Behalf Of Michael Houlberg
Sent: Monday, October 17, 2022 4:05 PM
To: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
Subject: Getting started with oAuth2
CAUTION: This email originated from outside of Pacific. Do not click any links or open attachments if this is unsolicited email.
I’m just having a hard time understanding how to use oAuth2 with the various OW3 workers. The part that is throwing me is understanding some of the parts. Specifically, Client ID, Client Secret, Authorize URL and Access Token URL.
I have an application I built for a client that is currently uses the IMAP, SMTP and SFTP. I’ve updated the SMTP and SFTP to use the OW3 Workers, (I still need to get the IMAP up to date). My client tells me that he needs to use oAuth2 now because Microsoft requires it. He has temporarily set his configuration to use the “old style” log in so it functions.
Are the Client ID and Client Secret something that I need to get one time from Microsoft for my application, or is this something that gets generated with each oAuth login? Or is this something my client knows and gives me?
If I understand, once I have these, I connect to the Authorize URL and receive an Access Token URL? At that point I think it gets hooked into the OW3 Worker for IMAP, SMTP and SFTP accordingly?
I know some of you have done this. I’ve seen that there are sample apps in the Omnis Hub Samples library. I’ve looked that those but there isn’t any real explanation.
Houlberg Development, LLC
Manage your list subscriptions at https://lists.omnis-dev.com Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
More information about the omnisdev-en