3 unstable releases

Uses old Rust 2015

0.3.0 May 18, 2018
0.2.1 Apr 6, 2018
0.2.0 Apr 6, 2018

#921 in Authentication

Download history 11/week @ 2024-02-16 10/week @ 2024-02-23 6/week @ 2024-03-01 4/week @ 2024-03-08 2/week @ 2024-03-15 46/week @ 2024-03-29 19/week @ 2024-04-05

65 downloads per month

MIT/Apache

13KB
166 lines

Google Sign-In for Rust

google-signin on crates.io google-signin on docs.rs

Rust API bindings for Google Sign-in.
See authenticating with a backend server.

Usage

Put this in your Cargo.toml:

[dependencies]
google-signin = "0.3.0"

And this in your crate root:

extern crate google_signin;

And then you can verify a google JSON web token

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 which handles most of the validation logic, but introduces some latency.

If you are expecting high volumes of sign-ins:

Dependencies

~5–7.5MB
~192K SLoC