Hi Richard,
i had a similar issue with another oauth service (not sure if microsoft based),
the problem was inside the handler OAuth2Refresh, the pRefreshToken was already
urlencoded.
I only changed this line:
put "_token=" & pRefreshToken after tParams
This solved my problem.
command
Thanks for confirming my hunch about the redirect URI.
I've passed along a localhost string to the Azure admin with a port
specifier that matches the one I'm passing into the lib. Still no go -
same result, no browser widget close.
One possible issue: the admin tells me the Azure admin UI
May be related but I’m having an issue with an old script returning cancel with
oauth2 lib today - can’t debug will check in morning
On 30 Jun 2020, 23:19 +0100, Monte Goulding via use-livecode
, wrote:
> It does sound like an issue with the redirect uri.
>
> Perhaps a configuration issue in
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
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
