Google OAuth 2.0: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 10: | Line 10: | ||
GET /o/oauth2/iframerpc?action=checkOrigin&origin=http%3A%2F%2Fnombp3.local%3A3002&client_id=7777777777777-a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a.apps.googleusercontent.com | GET /o/oauth2/iframerpc?action=checkOrigin&origin=http%3A%2F%2Fnombp3.local%3A3002&client_id=7777777777777-a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a.apps.googleusercontent.com | ||
client_id value is hardcoded in the client application. |
Revision as of 21:44, 16 May 2019
Internal
Call Sequence
Experimental:
GET /o/oauth2/iframe
GET /o/oauth2/iframerpc?action=checkOrigin&origin=http%3A%2F%2Fnombp3.local%3A3002&client_id=7777777777777-a7a7a7a7a7a7a7a7a7a7a7a7a7a7a7a.apps.googleusercontent.com
client_id value is hardcoded in the client application.