![]() ![]() Is forced to link their account again after a token expires with the implicitįlow. This exchange happens when Google needs a new access token because theĪlthough the implicit flow is simpler to implement, Google recommends thatĪccess tokens issued by the implicit flow never expire. Exchanges a long-lived refresh token for a short-lived access token.Exchanges an authorization code for a long-lived refresh token and a.The token exchange endpoint, which is responsible for two types of Short-lived authorization code to record users' consent to the requested The authorization endpoint also creates a The authorization endpoint, which presents the sign-in UI to your users In the authorization code flow, you need two endpoints: This access token is now included in every request sent from Google. After successful sign in, you return a long-lived access token to In the implicit flow, Google opens your authorization endpoint in the user'sīrowser. Your service must support OAuth 2.0 compliantĪuthorization and token exchange endpoints. Accounts are linked using industry standard OAuth 2.0 implicit andĪuthorization code flows. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |