We recommend the following libraries and samples to help you implement the OAuth 2.0 flow
Or Sign-In on TVs and Limited Input Devices. Implement than the lower-level protocol described here.įor apps running on devices that do not support a system browser or that have limited inputĬapabilities, such as TVs, game consoles, cameras, or printers, see Responses from Google's authorization server.įor mobile apps, you may prefer to use Google Sign-in forĬlient libraries handle authentication and user authorization, and they may be simpler to That installed apps must open the system browser and supply a local redirect URI to handle This authorization flow is similar to the one used for They can access Google APIs while the user is present at the app or when Installed apps are distributed to individual devices, and it is assumed that these appsĬannot keep secrets. Users to store files in their Google Drives. Usernames, passwords, and other information private.įor example, an application can use OAuth 2.0 to obtain permission from OAuth 2.0 allows users to share specific data with an application while keeping their This document explains how applications installed on devices like phones, tablets, andĬomputers use Google's OAuth 2.0 endpoints to authorize access to You've selected the right flow for your application. Overview summarizes OAuth 2.0 flows that Google supports, which can help you to ensure that OAuth 2.0 overview before getting started. Note: If you are new to OAuth 2.0, we recommend that you read the
0 kommentar(er)
