Skip to content

Document Google Desktop token-endpoint client secret #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sukujgrg merged 1 commit into from
Aug 16, 2026
Merged

Document Google Desktop token-endpoint client secret #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion skills/oauth2c/reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,10 @@ usable at `/userinfo`.
or `http://[::1]`. The `redirect_uri` in authorize and token must still
include the port the app actually bound. oauth2c does not bind `:0` and
rewrite `redirect_uri`; use a fixed port. To see any-port policy, run
two fixed ports. Google Web clients are exact-match, like Auth0.
two fixed ports. Google issues a `client_secret` for Desktop apps; send
it on the token request with `--auth-method client_secret_post`. PKCE
does not replace that. Do not use the skill’s public recipe
(`--auth-method none`). Google Web clients are exact-match, like Auth0.

## Auth0 demo env

Expand Down