Skip to content
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.

Wrong recipient, payload audience != requiredAudience #2

Open
skryshtafovych opened this issue Sep 4, 2019 · 3 comments
Open

Wrong recipient, payload audience != requiredAudience #2

skryshtafovych opened this issue Sep 4, 2019 · 3 comments

Comments

@skryshtafovych
Copy link

skryshtafovych commented Sep 4, 2019

Been trying to figure out what is wrong in my code since Tut does not follow newest changes in UI. Now i am running into Issue Below pleases suggest workaround. Also Which Client ID should i Use since doc not in Sync.

This error seems to occur after "Privacy Policy MSG" is displayed

Error: Wrong recipient, payload audience != requiredAudience
    at OAuth2Client.verifySignedJwtWithCerts (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:696:23)
    at OAuth2Client.<anonymous> (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:514:38)
    at step (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:57:23)
    at Object.next (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:38:53)
    at fulfilled (/srv/node_modules/google-auth-library/build/src/auth/oauth2client.js:29:58)
    at <anonymous>
    at process._tickDomainCallback (internal/process/next_tick.js:229:7)

@MaltesBytes
Copy link

Same issue here

@ghost
Copy link

ghost commented Jul 22, 2022

Found any solution ?

@aaron-cardenas
Copy link

The problem here is the client_id that is being used to create an OAuth2Client and the client_id being used as the audience in the verifyIdToken is not the same. The client_id for the audience should be the client_id that was used in your frontend application to get the id_token.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants