Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I believe when you sign in with Google, the web application running in your browser calls a command to request the Google Sign In page, and includes a “callback URL” as a parameter in that HTTP req...
#2: Post edited
by
Julius H.
·
2024-02-13T22:26:42Z (10 months ago)
- I believe when you sign in with Google, the web application running in your browser calls a command to request the Google Sign In page, and includes a “callback URL” as a parameter in that HTTP request.
- When successful, that Google page running in your browser calls the callback URL, and includes an authentication token as a parameter in the HTTP request.
- What is that authentication token used for?
- Is it used to permit future calls to your Google profile info, like API calls for name, profile picture, etc.?
- Or is it stored as an identification token, like a hashed password, in the user database? (If so, do you receive the same token every time you log in with Google from that same app in the future?)
If I understand correctly, when you use SSO (single sign-on) in an authentication framework like Omniauth, communication with the SSO service
- I believe when you sign in with Google, the web application running in your browser calls a command to request the Google Sign In page, and includes a “callback URL” as a parameter in that HTTP request.
- When successful, that Google page running in your browser calls the callback URL, and includes an authentication token as a parameter in the HTTP request.
- What is that authentication token used for?
- Is it used to permit future calls to your Google profile info, like API calls for name, profile picture, etc.?
- Or is it stored as an identification token, like a hashed password, in the user database? (If so, do you receive the same token every time you log in with Google from that same app in the future?)
#1: Initial revision
by
Julius H.
·
2024-02-13T22:25:08Z (10 months ago)
What happens when you “Sign in with Google”?
I believe when you sign in with Google, the web application running in your browser calls a command to request the Google Sign In page, and includes a “callback URL” as a parameter in that HTTP request. When successful, that Google page running in your browser calls the callback URL, and includes an authentication token as a parameter in the HTTP request. What is that authentication token used for? Is it used to permit future calls to your Google profile info, like API calls for name, profile picture, etc.? Or is it stored as an identification token, like a hashed password, in the user database? (If so, do you receive the same token every time you log in with Google from that same app in the future?) If I understand correctly, when you use SSO (single sign-on) in an authentication framework like Omniauth, communication with the SSO service