OAuth 1.0a Provider with Redis in Python
I want to build a scalable OAuth 1.0a Provider that is is to subclass specifically in authenticating users against various databases. Focuses in leveraging performance by using Redis as the primary OAuth Provider backend, user authentications can be handled differently using any other databases.
Compatibility Against RFC5849 <http://tools.ietf.org/html/rfc5849>
With this README, I have no plans in supporting 3 legged authentications. I am only supporting XAuth at the moment. Fork and contribute to add support to 3 legged authentications.
OAuth Authorization components are all expected from a HTTP POST body except for OAuth Signatures, this is expected from query strings.
Will refactor later on, it seems that my REST tool is not supporting extra Authentication headers properly.
Using
Don’t! Not yet.
1 maintainer
Metadata
1 maintainer
Release files for oauth1-provider 0.1.0
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 |
|---|---|---|---|---|
| oauth1-provider-0.1.0.tar.gz | 3.5 kB | Without provenance | Details for oauth1-provider-0.1.0.tar.gz |
Release files / oauth1-provider-0.1.0.tar.gz
| Download URL | oauth1-provider-0.1.0.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48c374b22d0ec84e3a181fe385bfe8ccdf9ad70c3d74c71fc20a736b11910e5d
|
|
BLAKE2b-256 checksum How to use checksums |
32243ffc870db97f794616ad00145a092c1d3ba673883fd1417cd0f1dd8d21b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for oauth1-provider 0.1.0
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.
