|
|
|
|
|
by CobrastanJorji
3311 days ago
|
|
I'm no expert on Google OAuth, so this could be wrong, but my understanding is that this is totally fine. The client secret is, despite its name, not necessarily intended to be secret. Client ID / secret pairs can be locked down to only work with specific referer headers or Application IDs. Also, they are only useful for purposes of quota and don't provide authentication. A malicious entity could make calls against the quota of this app (which is true for any app), but they couldn't easily distribute the key or use it for other purposes very well. |
|