3aadc6b0ef
1) Remove the GetToken trait. The trait seemed to be organically designed. It appeared to be mostly tailored for simplifying the implementation since there was no way for users to provide their own implementation to Authenticator. It sadly seemed to get in the way of implementations more than it helped. An enum representing the known implementations is a more straightforward way to accomplish the goal and also has the benefit of not requiring Boxing when returning features (which admittedly is a minor concern for this use case). 2) Reduce the number of type parameters by using trait object for delegates. This simplifies the code considerably and the performance impact of virtual dispatch for the delegate calls is a non-factor. 3) With the above two simplifications it became easier to unify the public interface for building an authenticator. See the examples for how InstalledFlow, DeviceFlow, and ServiceAccount authenticators are now created.
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).
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, ...
Usage
Please have a look at the API landing page for all the examples you will ever need.
A simple commandline program which authenticates any scope and prints token information can be found in the examples directory.
The video below shows the auth example in action. It's meant to be used as utility to record all server communication and improve protocol compliance.
Versions
Version 1.x for Hyper versions bellow 12 Version 2.x for Hyper versions 12 and above
License
Licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
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.