Open yashomi-t3h opened 1 month ago
Seems the wasp-lang only supports HMAC algorithm. Google oauth returns only RSA based Id_tokens. Is there any way to get around this when using chrome extension?
Related to: https://ptb.discord.com/channels/686873244791210014/1286743756594352228/1286743756594352228 continuing there.
I am planning to develop chrome extenstion where the user is required to sign in using google oauth. For extension to initiate flow it would call a method called chrome.identity.launchWebAuthFlow
From this call I am able to fetch code, access_token and id_token
https://.chromiumapp.org/#state=8v9lwh
&code= "code starting with 4 "
&access_token="starting with ya29"
&id_token="starting with ey"
I see in browser when doing oAuth you use the IDtoken and exchange it via API using following request to get the bearer token. However this gives me error for the token I recieved using chrome extention ( method chrome.identitylauchWebflow)
Error details are as below
Not able to understand where it is going wrong?