Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. COThank you! With OAuth 2.0, I haven't so far found out how to identify whether the user has an active session with Google or not and if he does, what his active session id (a "claimed_id" or unique Google id) is, without ever showing him anything. This is necessary because I need to see if he has an active account with us when he goes to log in, and if he does, to ensure his account doesn't get "re-created" in our database every time he logs in. I still want to store data related to his account locally somehow on my database server. (character limit..I'll have to comment twice.)
      singulars
    2. COAnd I have seen that page, and have implemented some aspects of OAuth 2.0 (I guess just API access) into my site, but I have some concerns about this. It seems like identity and API authorization can't be done "concurrently to the user" (one prompt total) with OAuth 2.0, which I'm assuming was the whole motive for the Hybrid approach, or am I wrong? I have read through almost every page on Google's Dev docs and I'm still confused because I don't have practical experience with this.
      singulars
    3. COYes, you can get access to both identity and additional information (such as YouTube videos, contacts, Google Drive) in 1 prompt in the user's lifetime. You simply specify the multiple scopes you need. The user will be prompted the first time you request access to their info, and only the first time. Of course, you won't get their unique Google ID until after they've approved the request the first-time. But on subsequent requests, it'll be a redirect to Google, then an immediate redirect back to your app with either an authorization code or an access token (depending on flow you choose).
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload