google-signin 0.3.0

API bindings for Google Sign-In
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51

Google Sign-In for Rust
=======================

[![google-signin on crates.io](https://img.shields.io/crates/v/google-signin.svg)](https://crates.io/crates/google-signin)
[![google-signin on docs.rs](https://docs.rs/google-signin/badge.svg)](https://docs.rs/google-signin)

Rust API bindings for Google Sign-in.  
See [authenticating with a backend server](https://developers.google.com/identity/sign-in/web/backend-auth).

## Usage
Put this in your `Cargo.toml`:

```toml
[dependencies]
google-signin = "0.3.0"
```

And this in your crate root:

```rust
extern crate google_signin;
```

And then you can verify a google JSON web token

```rust
use google_signin;
let mut client = google_signin::Client::new();
client.audiences.push(YOUR_CLIENT_ID); // required
client.hosted_domains.push(YOUR_HOSTED_DOMAIN); // optional

// Let the crate handle everything for you
let id_info = client.verify(&data.token).expect("Expected token to be valid");
println!("Success! Signed-in as {}", id_info.sub);

// Inspect the ID before verifying it
let id_info = client.get_slow_unverified(&data.token).expect("Expected token to exist");
let ok = id_info.verify(&client).is_ok();
println!("Ok: {}, Info: {:?}", ok, id_info);
```

## Other Notes
The `verify` function currently uses the
[tokeninfo endpoint](https://developers.google.com/identity/sign-in/web/backend-auth#calling-the-tokeninfo-endpoint)
which handles most of the validation logic, but introduces some latency.

If you are expecting high volumes of sign-ins:
 * Add a reaction to the
[Handle Certificate and Cache-Control auth flow](https://github.com/wyyerd/google-signin-rs/issues/2)
issue so we know how many people need it.
 * OR, Submit a Pull Request for the issue to help out.