This may be too obvious, but with OAuth on Google APIs I found I had to add
(or was it remove) a trailing slash on the redirect. Also that localhost
didn't work. E.g. only one of
http://127.0.0.1:56789
http://127.0.0.1:56789/
and definitely not
On 7/22/20 12:00 PM, Richard Gaskin via use-livecode wrote:
Oddly, it appears as though we're authentincating fine as it is using
shared secret, the only problem being that we're not getting the
redirect to close the browser widget and return the auth code to us.
What happens if you try
On 7/22/20 11:55 AM, Richard Gaskin via use-livecode wrote:
And I missed something - how does Amazon play into this?
Sorry - my bad. Doing too many things at once here.
--
Mark Wieder
ahsoftw...@gmail.com
___
use-livecode mailing list
A moment ago I wrote:
Mark Wieder wrote:
On 7/22/20 9:26 AM, Richard Gaskin via use-livecode wrote:
I've run into a snag in which the OAuth2 redirect URI does not seem to
be called when used to authenticate for Microsoft API services such as
Dynamics 365.
Before getting into details (there
Mark Wieder wrote:
On 7/22/20 9:26 AM, Richard Gaskin via use-livecode wrote:
I've run into a snag in which the OAuth2 redirect URI does not seem to
be called when used to authenticate for Microsoft API services such as
Dynamics 365.
Before getting into details (there are many) it would be
On 7/22/20 9:26 AM, Richard Gaskin via use-livecode wrote:
I've run into a snag in which the OAuth2 redirect URI does not seem to
be called when used to authenticate for Microsoft API services such as
Dynamics 365.
Before getting into details (there are many) it would be helpful to know
