This package provides the original implementation of the pluggable authentication utility. It has been superceded by zope.app.authentication.
Detailed Dcoumentation
New Authentication Service Design
The current implementation will be replaced. The following is a design I came up with together with Jim Fulton. – itamar
Note that this design is implemented (in some form) by the pluggable auth service. This document needs to be updated to reflect the final implementation.
Design notes for new AuthenticationService
The service contains a list of user sources. They implement interfaces, starting with:
class IUserPassUserSource:
"""Authenticate using username and password."""
def authenticate(username, password):
"Returns boolean saying if such username/password pair exists"
class IDigestSupportingUserSource(IUserPassUserSource):
"""Allow fetching password, which is required by digest auth methods"""
def getPassword(username):
"Return password for username"
etc. Probably there will be others as well, for dealing with certificate authentication and what not. Probably we need to expand above interfaces to deal with principal titles and descriptions, and so on.
A login method (cookie auth, HTTP basic auth, digest auth, FTP auth), is registered as a view on one of the above interfaces.
class ILoginMethodView:
def authenticate():
"""Return principal for request, or None."""
def unauthorized():
"""Tell request that a login is required."""
The authentication service is then implemented something like this:
class AuthenticationService:
def authenticate(self, request):
for us in self.userSources:
loginView = getView(self, us, "login", request)
principal = loginView.authenticate()
if principal is not None:
return principal
def unauthorized(self, request):
loginView = getView(self, self.userSources[0], request)
loginView.unauthorized()
CHANGES
3.4.0 (2007-10-25)
Initial release independent of the main Zope tree.
Metadata
Release files for zope.app.pluggableauth 3.4.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 | |
|---|---|---|---|---|
| zope.app.pluggableauth-3.4.0.tar.gz | 12.5 kB | Without provenance | Details |
Release files / zope.app.pluggableauth-3.4.0.tar.gz
| Download URL | zope.app.pluggableauth-3.4.0.tar.gz |
|---|---|
| Size | 12.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
54611d1ed3ab04ab7fbc85cd6dc6e9193073bfaf14b6f81e9a4ee76cea1ad3f2
|
|
BLAKE2b-256 checksum How to use checksums |
3e0ffef14d2e3e91d3577101756dcb951c9a0f62522bd201b3a342de7577449c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for zope.app.pluggableauth 3.4.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.