#oauth #google #google-api #google-service #http-request #v2 #generate

yup-oauth2

An oauth2 implementation, providing the 'device', 'service account' and 'installed' authorization flows

92 releases (53 stable)

new 8.3.3 Mar 20, 2024
8.3.2 Dec 27, 2023
8.3.0 Apr 22, 2023
8.1.0 Dec 2, 2022
0.3.1 Mar 22, 2015

#2309 in Network programming

Download history 52617/week @ 2023-12-06 51620/week @ 2023-12-13 36474/week @ 2023-12-20 17290/week @ 2023-12-27 40620/week @ 2024-01-03 36007/week @ 2024-01-10 52043/week @ 2024-01-17 63260/week @ 2024-01-24 60650/week @ 2024-01-31 59182/week @ 2024-02-07 56080/week @ 2024-02-14 54991/week @ 2024-02-21 64173/week @ 2024-02-28 57452/week @ 2024-03-06 60557/week @ 2024-03-13 44931/week @ 2024-03-20

238,867 downloads per month
Used in 763 crates (134 directly)

MIT/Apache

155KB
3K SLoC

Build Status crates.io

yup-oauth2 is a utility library which implements several OAuth 2.0 flows. It's mainly used by google-apis-rs, to authenticate against Google services. (However, you're able to use it with raw HTTP requests as well; the flows are implemented as token sources yielding HTTP Bearer tokens). Note that the newer, asynchronous versions of this crate (version 4) are not compatible with google-apis-rs anymore/at the moment.

To use asynchronous APIs with the new yup-oauth2 (from version 4), use the async-google-apis code generator, which generates asynchronous API stubs for Google APIs and other providers who provide Discovery documents for their REST APIs. (WARNING: that project is still alpha-quality. Contributions are welcome)

The provider we have been testing the code against is also Google. However, the code itself is generic, and any OAuth provider behaving like Google will work as well. If you find one that doesn't, please let us know and/or contribute a fix!

Supported authorization types

  • Device flow (user enters code on authorization page)
  • Installed application flow (user visits URL, copies code to application, application uses code to obtain token). Used for services like GMail, Drive, ...
  • Service account flow: Non-interactive authorization of server-to-server communication based on public key cryptography. Used for services like Cloud Pubsub, Cloud Storage, ...

Versions

  • Version 1.x for Hyper versions below 12
  • Version 2.x for Hyper versions 12 and above
  • Version 3.x for historical interest
  • Version 4.x for tokio 0.2/0.3
  • Version 5.x for tokio 1.0

License

Licensed under either of

at your option.

Contribution

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.

Dependencies

~11–26MB
~414K SLoC