This page (revision-1) was last changed on 29-Nov-2024 16:16 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 1 added 35 lines
!!! Overview [TODO] needs more verification
!! [{$pagename}] and [OAuth 2.0]
[{$pagename}] involves setting up: [1]
%$%prettify
{{{
http://127.0.0.1:port
or
http://::1:port
}}} /%
http://127.0.0.1:port or http://::1:port
You should query your platform for the relevant loopback IP, and start an HTTP listener on a random available port, Substitute port for the actual port number you are listening on.
Recommended Usage:
* macOS
* Linux
* Windows desktop
** but not Universal Windows Platform apps.
Client Type:
* Register with type Other.
To receive the [Authorization Code] using this URL, your [application|OAuth Client] must be listening on the local web server. This is possible on many, but not all, platforms. If your platform supports it this is the __recommended__ mechanism for obtaining the [Authorization Code].
When your [application|OAuth Client] receives the [authorization Response], for best usability, it should respond with an [HTML] page, instructing the user to close the browser tab and return to your [application|OAuth Client].
Note: It is also possible to use [localhost] in place of the loopback IP, but this may cause issues with client firewalls. Most firewalls allow loopback communication, though this may not always be the case.
!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]
----
* [#1] - [Using OAuth 2.0 for Mobile and Desktop Applications|https://developers.google.com/identity/protocols/OAuth2InstalledApp/|target='_blank'] - based on information obtained 2016-07-05