(04-06-2022, 09:54 PM)Boba TC Wrote: well... I am using that link and the link clearly says "To start the sign-in process ..., use a web browser or web-browser control to load a URL request."
OAuth does involve a small portion that requires user interaction to transit their credentials and get a token back, but the rest of the OAuth protocol can be handled by any HTTP library.
(04-06-2022, 09:54 PM)Boba TC Wrote: What I do not understand is: if Indy TIdHTTP component is basically a socket,
so how do I run the script sent back in the reply to my request.
You can't. It needs to be run by a scripting engine, which is outside the scope of Indy.
(04-06-2022, 09:54 PM)Boba TC Wrote: It is that script that generates what I see when MS reply is viewed as HTML file.
You will have to use an embedded browser, such as TWebBrowser or TEdgeBrowser.
(04-06-2022, 09:54 PM)Boba TC Wrote: There has to be a way to log-in with no browser usage; am I wrong?
Yes, you are. At least a portion of the OAuth protocol requires a web browser.