repoze.who
repoze.who is an identification and authentication framework for arbitrary WSGI applications. repoze.who can be configured either as WSGI middleware or as an API for use by an application.
repoze.who is inspired by Zope 2’s Pluggable Authentication Service (PAS) (but repoze.who is not dependent on Zope in any way; it is useful for any WSGI application). It provides no facility for authorization (ensuring whether a user can or cannot perform the operation implied by the request). This is considered to be the domain of the WSGI application.
Installation
Install using pip (within a virtualenv):
$ pip install repoze.who
Usage
For details on using the various components, please see the documentation in docs/index.rst. A rendered version of that documentation is also available online:
Reporting Bugs
Please report bugs in this package to
Obtaining Source Code
Download development or tagged versions of the software by visiting:
Release files for repoze.who 3.2.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 |
|---|---|---|---|---|
| repoze_who-3.2.0.tar.gz | 295.5 kB | With provenance | Details for repoze_who-3.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| repoze_who-3.2.0-py3-none-any.whl | Python 3 | none | any | Details for repoze_who-3.2.0-py3-none-any.whl |
Total release size: 324.4 kB
Release files / repoze_who-3.2.0.tar.gz
| Download URL | repoze_who-3.2.0.tar.gz |
|---|---|
| Size | 295.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1d756fd04d17c291303bf9777da11c052cac795a4d3e82569e250a76c72d28c
|
|
BLAKE2b-256 checksum How to use checksums |
fe417519937691bc77bf7e560dbd3210eaafcc06327eadfb3cffab0a331d8c58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 17, 2026.
Transparency logRelease files / repoze_who-3.2.0-py3-none-any.whl
| Download URL | repoze_who-3.2.0-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b96b915aa8494e3ee610120c645cf24713cda2f874d841c88d9f064a7f28b73c
|
|
BLAKE2b-256 checksum How to use checksums |
e71eb7bcc009955689db92793886ed1c72d7bf0f6a0ea6c6983222cd9f510663
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 17, 2026.
Transparency logSecurity for repoze.who 3.2.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for repoze_who-3.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 17, 2026.
Transparency logA 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.
