'Saving Google Client ID for Sign with in Google for my api
So according to the Google documentation for integrating Google signin with your api, you are to generate an oauth client and copy and save its clientId in your api. So when a client sends you an IdToken generated, you use the clientId and idToken to retrieve the user's profile
Key thing I noticed from testing is that clientId used to generate the IdToken on the client must be the same with the clientId used on the api for the profile retrieval to be successful on the api.
So my question is, if the client's clientId must be the same on the client and on the api, isn't it better for the client to just send in their client Id for the api to use, instead of the api managing another clientId as well?
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|