Support library to be used with bitly/oauth2_proxy to validate and decode the Cookie passed upstream. The library provide a Flask extension to authorize requests based on the Cookie.
The reference implementation in Go is located here.
Example
from flask import request, abort
from oauth2_proxy_cookie import Validator
secret = <oauth2_proxy cookie secret>
validator = Validator(secret, '_oauth2_proxy')
cookie = request.headers.get('Cookie')
value, time = validator.validate(cookie)Or with Flask extension:
from flask import request, abort
from oauth2_proxy_cookie import Validator
app = flask.Flask('Foo')
oauth2_proxy = OAuth2ProxyCookie()
oauth2_proxy.init_app(app, allowed=['/public_path'])1 maintainer
Metadata
1 maintainer
Release files for oauth2-proxy-cookie 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 |
|---|---|---|---|---|
| oauth2-proxy-cookie-0.1.0.tar.gz | 2.9 kB | Without provenance | Details for oauth2-proxy-cookie-0.1.0.tar.gz |
Security for oauth2-proxy-cookie 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.
