OAuth2 on Win10: not returning to my app

[Monte Goulding]

It does sound like an issue with the redirect uri.

Perhaps a configuration issue in your app on the endpoint? Some endpoints will use the redirect uri from the request, some will ensure it matches perfectly with your settings for your app on their portal, some will just use the redirect in the portal settings.

Whatever is happening, there is no HTTP request to localhost on your specified port because if there was the dialog would close by itself.

> On 30 Jun 2020, at 6:14 am, Richard Gaskin via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> I've been working with the Oauth2 lib included with v9 (superhandy, team, thanks!), and I've run into a snag:
> 
> When I call it, the browser widgets opens and goes to the authentication provider (in this case Office 365), and authentication seems to work well.
> 
> However, at that point I'd expect the browser widget's window to close and "it" would contain the approved auth scope info.
> 
> Instead what I'm seeing is the browser widget window remains open, and it redirects into my Office 365 account.  I can close the window manually with the "Cancel" button, but then "it" in my calling script contains "Cancel", no auth info.
> 
> Have any of you successfully used LC's OAuth2 lib to log into MS Office 365 or other MS product that uses OAuth?
> 
> If so, what did you use for the redirect URL?  Or is there something else I should be considering?
> 
> TIA -
> 
> -- 
> Richard Gaskin
> Fourth World Systems
> Software Design and Development for the Desktop, Mobile, and the Web
> ____________________________________________________________________
> Ambassador at FourthWorld.com                http://www.FourthWorld.com
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode