https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto
| gRPC Code | HTTP Status Code |
|---|---|
| OK = 0 | 200 OK |
| CANCELLED = 1 | 499 Client Closed Request |
| UNKNOWN = 2 | 500 Internal Server Error |
| INVALID_ARGUMENT = 3 | 400 Bad Request |
https://github.com/googleapis/googleapis/blob/master/google/rpc/code.proto
| gRPC Code | HTTP Status Code |
|---|---|
| OK = 0 | 200 OK |
| CANCELLED = 1 | 499 Client Closed Request |
| UNKNOWN = 2 | 500 Internal Server Error |
| INVALID_ARGUMENT = 3 | 400 Bad Request |
This is another piece of code I've extrapolated from a Ruby on Rails project I'm currently working on. The code implmenets social login with a RoR API-based application, targeted at API clients.
The setup does not involve any browser-redirects or sessions as you would have to use working with Omniauth.
Instead, what it does is takes an access_token generated on client-side SDKs, retireves user info from the access token
and creates a new user and Identity in the database.
This setup works with native applications as described in the Google iOS Sign In Docs (see Authenticating with a backend server)