This is the basic OAuth flow that sends users to your website for linking. The user is redirected to your website to sign in to their account. Once signed in, the user consents to sharing their data, on your service, with Google. At that point, the user's Google Account and your service, are linked. OAuth Linking supports the authorization code and implicit OAuth flows.
Your service must host an OAuth 2. OAuth-based App Flip Linking guides users as they move between your verified Android or iOS mobile apps and Google's platform to review the proposed data access changes and grant their consent to link their account on your platform with their Google account.
App Flip is supported for both Android and iOS. OAuth-based Google Sign-In Streamlined linking adds Google Sign-In on top of OAuth linking, enabling users to complete linking the linking process without leaving the Google surface, thereby reducing frictions and drop-offs.
OAuth-based Streamlined Linking offers the best user experience with seamless sign-in, account creation and account linking by combining Google Sign-in with OAuth linking. Your service must support OAuth 2. We recommend implementing all flows to ensure users get the best linking experience. The Streamlined and App flip flows reduce linking friction as users are able to complete the linking process in very few steps. The Web OAuth linking has the lowest level of effort and is a good place to start after which you can add on the other linking flows.
You issue access tokens to Google for individual Google Accounts after obtaining account holders consent to link their accounts and share data. OAuth 2. Authorization code. A short-lived token that can be exchanged for an access and a refresh token. For security purposes, Google calls your authorization endpoint to obtain a single use or very short-lived code. Access token. A token that grants the bearer access to a resource. To limit exposure that could result from the loss of this token, it has a limited lifetime, usually expiring after an hour or so.
Refresh token. A long-lived token that can be exchanged for a new access token when an access token expires. When your service integrates with Google, this token is exclusively stored and used by Google. Google calls your token exchange endpoint to exchange refresh tokens for access tokens, which are in turn used to access user data.
Race conditions in clustered environments and client-server exchanges can result in complex timing and error handling scenarios when working with tokens. For example:. Requests and replies can arrive in any order, or not at all due to asynchronous services running in a cluster, network behavior, or other means. Immediate and fully consistent shared state both within, and between, your and Google's token handling systems cannot be guaranteed. Multiple valid, unexpired tokens can coexist within or across systems short period of time.
To minimize negative user impact we recommend you do the following:. During maintenance or unplanned outages Google might be unable to call your authorization or token exchange endpoints to obtain access and refresh tokens. Your endpoints should respond with a error code and empty body. In this case, Google retries failed token exchange requests for a limited time. Provided that Google is later able to obtain refresh and access tokens, failed requests are not visible to users.
Failing requests for an access token result in a visible error, if initiated by a user. Users will be required to retry linking failures if the implicit OAuth 2. Maintain your existing service and route a limited number of requests to your newly updated service.
Migrate all requests only after confirming expected functionality. We'll need details of your OAuth 2. See registration for details. Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4. For details, see the Google Developers Site Policies. Google Identity. Overview OAuth 2. Android One Tap. Web Sign In With Google. Smart Lock for Android. Additionally, you can link your Google account to a separate email address if you wish. It is possible to use YouTube without a Google account.
Without a Google account, you can view videos on YouTube that do not have age restrictions. However, in order to view videos with age restrictions, you must be logged in to your Google account. Furthermore, you will not be able to comment on, like, or upload videos to YouTube without a Google account. Before , YouTube and Google accounts were separate entities.
Therefore, some users may have separate accounts for both services. In this case, these accounts are not necessarily linked. These accounts, called "legacy accounts", can be linked and unlinked at will.
In this way, YouTube accounts do not necessarily require Google accounts. Serm Murmson is a writer, thinker, musician and many other things. He has a bachelor's degree in anthropology from the University of Chicago. His concerns include such things as categories, language, descriptions, representation, criticism and labor.
0コメント