parse-community / parse-community/parse-server

Issue obtaining a valid JWT from Google Oauth2 Sign in

Open
#6,849 26 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type:bug type:docs
Dominant language
JavaScript
Stars
21.4k
Forks
4.8k
Avg merge
7h 45m
Merged PRs (30d)
11

Description

Im using your Google Auth adapter for web login. my call to google yields an access_token (rather than ID token), the token is not a standard JWT and looks like the following : ya29.a0AfH6SMDBFlJErplnG3niNU_qksL9yyOfbbYJO5DF7uDPGVpIx4ef6CEBfxZ00QBDdDeLtOQsPQqzz57tn7AUwHxhO0vT0Lg49spIsaWgVkE_lWmhC29Kgcl-DueDWFdS8f57w5KLFusqvLtwlLCkNfAZIeqgJN6Kg_2

It seems that Google have updated their Oauth2 APIs, I also see you have updated your Google auth provider however it doesnt accept this as a valid JWT, is there some other way to authenticate with Google and Parse now ?

https://developers.google.com/identity/protocols/oauth2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Google Auth adapter/provider and the linked Google OAuth2 documentation, tracing the distinction between the supplied access token and an ID token. Confirm the authentication credential contract expected by Parse; done when a supported Google sign-in flow is identified and its expected token type is clear.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.