#oauth #server #oauth2


A OAuth2 library for common web servers, featuring a set of configurable and pluggable backends

21 releases

0.5.0-preview.0 Dec 23, 2019
0.4.5 Aug 20, 2019
0.4.3 Jun 3, 2019
0.4.2 Feb 15, 2019
0.1.0-alpha.1 Nov 29, 2017

#15 in Authentication

Download history 47/week @ 2019-10-04 2/week @ 2019-10-11 91/week @ 2019-10-18 24/week @ 2019-10-25 42/week @ 2019-11-01 6/week @ 2019-11-08 47/week @ 2019-11-15 12/week @ 2019-11-22 41/week @ 2019-11-29 117/week @ 2019-12-06 6/week @ 2019-12-13 15/week @ 2019-12-20 25/week @ 2019-12-27 5/week @ 2020-01-03 183/week @ 2020-01-10

166 downloads per month
Used in 4 crates




A OAuth2 server library, for use in combination with actix or other frontends, featuring a set of configurable and pluggable backends.


oxide-auth aims at providing a comprehensive and extensible interface to managing oauth2 tokens on a server. While the core package is agnostic of the used frontend, an optional actix and a rouille adaptor is provided with the default configuration. Through an interface designed with traits, the frontend is as easily pluggable as the backend.


$ cargo run --example actix

In the example folder you can find an interactive example. This configures a server, registers a public client and initializes a resource requiring an authorization token. A client is also activated which can be used to access the resource. The example assumes the user to be the validated resource owner, who can deny or allow the request by the client.


These server libraries are integrated:

Name Feature Notes
actix actix-frontend, default Still 0.7, includes integration into messages
rocket rocket-frontend, nightly -
rouille rouille-frontend -
iron iron-frontend -


Crates.io Status Docs.rs Status License CI Status

A more or less comprehensive list of changes is contained in the changelog. Sometimes less as larger releases and reworks profit from a rough overview of the changes more than a cumulative list of detailed features.

For some hints on upgrading from older versions see the migration notes.

More information about contributing. Please respect that I maintain this on my own currently and have limited time. I appreciate suggestions but sometimes the associate workload can seem daunting. That means that simplifications to the workflow are also highly appreciated.

The code is MIT licensed. The license applies to all parts of the source code, its documentation and supplementary files unless otherwise indicated. It does NOT apply to the replicated full-text copies of referenced RFCs which were included for the sake of completion. These are distributed as permitted by IETF Trust License 4–Section 3.c.i.


~323K SLoC