A generic, spec-compliant, thorough implementation of the OAuth request-signing logic.
OAuth often seems complicated and difficult-to-implement. There are several prominent libraries for handling OAuth requests, but they all suffer from one or both of the following:
They predate the OAuth 1.0 spec, AKA RFC 5849.
They predate the OAuth 2.0 spec, AKA RFC 6749.
They assume the usage of a specific HTTP request library.
OAuthLib is a generic utility which implements the logic of OAuth without assuming a specific HTTP request object or web framework. Use it to graft OAuth client support onto your favorite HTTP library, or provider support onto your favourite web framework. If you’re a maintainer of such a library, write a thin veneer on top of OAuthLib and get OAuth support for very little effort.
Documentation
Full documentation is available on Read the Docs. All contributions are very welcome! The documentation is still quite sparse, please open an issue for what you’d like to know, or discuss it in our G+ community, or even better, send a pull request!
Interested in making OAuth requests?
Then you might be more interested in using requests which has OAuthLib powered OAuth support provided by the requests-oauthlib library.
Which web frameworks are supported?
The following packages provide OAuth support using OAuthLib.
For Django there is django-oauth-toolkit, which includes Django REST framework support.
For Flask there is flask-oauthlib and Flask-Dance.
If you have written an OAuthLib package that supports your favorite framework, please open a Pull Request, updating the documentation.
Using OAuthLib? Please get in touch!
Patching OAuth support onto an http request framework? Creating an OAuth provider extension for a web framework? Simply using OAuthLib to Get Things Done or to learn?
No matter which we’d love to hear from you in our G+ community or if you have anything in particular you would like to have, change or comment on don’t hesitate for a second to send a pull request or open an issue. We might be quite busy and therefore slow to reply but we love feedback!
Chances are you have run into something annoying that you wish there was documentation for, if you wish to gain eternal fame and glory, and a drink if we have the pleasure to run into eachother, please send a docs pull request =)
License
OAuthLib is yours to use and abuse according to the terms of the BSD license. Check the LICENSE file for full details.
Changelog
OAuthLib is in active development, with the core of both OAuth 1 and 2 completed, for providers as well as clients. See supported features for details.
For a full changelog see CHANGELOG.rst.
2 maintainers
Metadata
2 maintainers
Release files for oauthlib 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| oauthlib-0.7.1.tar.gz | 106.5 kB | Without provenance | Details for oauthlib-0.7.1.tar.gz |
Release files / oauthlib-0.7.1.tar.gz
| Download URL | oauthlib-0.7.1.tar.gz |
|---|---|
| Size | 106.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
70d004c4030c1a5924508a3006654441f7862cec826fb87428c429c1806fe47c
|
|
BLAKE2b-256 checksum How to use checksums |
b700bd68b9ec123d3058a07d79822e52672f4d22faff5f3669d899ef4f0ac8b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for oauthlib 0.7.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
