Menu

OAuth 2.0 + PKCE Explained — What's Actually Happening Behind Google Identity and Firebase Auth
📰

OAuth 2.0 + PKCE Explained — What's Actually Happening Behind Google Identity and Firebase Auth

Reddit r/googlecloud·u/PreferenceNo9502·6 months ago
#b3EcJfa1
#oauth#google#auth#pkce#identity
Reading 0:00
15s threshold

If you've integrated Google Sign-In, Firebase Authentication, or Google Identity Platform into your app — you've been using OAuth 2.0 + PKCE without necessarily knowing it.

Google's own auth infrastructure is built on this spec, so understanding it makes configuring OAuth consent screens, scopes, and redirect URIs in GCP a lot less mysterious.

The video covers:

The full Authorization Code Flow — exactly what happens when a user clicks "Sign in with Google"

Why PKCE is required for web and mobile apps (public clients)

How code_verifier and code_challenge (SHA-256) protect against auth code interception

How Bearer tokens / ID tokens are issued and what your Cloud Run or GCP backend validates

Confidential vs public clients — relevant when setting up OAuth 2.0 credentials in GCP Console

Good foundation before working with Google Identity Platform, Firebase Auth, or any GCP service that uses OAuth-based access.

https://youtu.be/gEIfV3ZSt-8?si=HgbqVbJrKRYrmQpw

Happy to discuss GCP-specific OAuth setups…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.