10 releases

0.4.4 Oct 10, 2020
0.4.3 Jun 4, 2020
0.4.2 Jan 21, 2020
0.4.1 Dec 20, 2019
0.1.0 Jul 2, 2019

#24 in Authentication

Download history 439/week @ 2020-06-28 476/week @ 2020-07-05 441/week @ 2020-07-12 635/week @ 2020-07-19 802/week @ 2020-07-26 550/week @ 2020-08-02 583/week @ 2020-08-09 583/week @ 2020-08-16 499/week @ 2020-08-23 386/week @ 2020-08-30 375/week @ 2020-09-06 435/week @ 2020-09-13 292/week @ 2020-09-20 277/week @ 2020-09-27 426/week @ 2020-10-04 411/week @ 2020-10-11

2,070 downloads per month
Used in 2 crates


464 lines

🔐 tame-oauth

Build Status Latest version Docs Contributor Covenant Embark

tame-oauth is a small oauth crate that follows the sans-io approach.


  • You want to control how you actually make oauth HTTP requests

Why not?

  • The only auth flow that is currently implemented is the service account flow for GCP. Other flows can be added, but right now that is the only one we need.
  • There are several other oauth crates available that have many more features and are easier to work with, if you don't care about what HTTP clients they use.
  • This crate requires more boilerplate to use.



Usage: cargo run --example svc_account -- <key_path> <scope..>

A small example of using tame-oauth together with reqwest. Given a key file and 1 or more scopes, it will attempt to get a token that could be used to access resources in those scopes.

cargo run --example svc_account -- ~/.secrets/super-sekret.json https://www.googleapis.com/auth/pubsub https://www.googleapis.com/auth/devstorage.read_only


We welcome community contributions to this project.

Please read our Contributor Guide for more information on how to get started.


Licensed under either of

at your option.


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


~147K SLoC