Sitting on the top the zope.pluggableauth package, dolmen.authentication extends it to add reusable component descriptions and implementations.
Overview
dolmen.authentication provides interfaces and components:
>>> import dolmen.authentication >>> from dolmen.authentication import IAuthenticationInterfaces >>> from dolmen.authentication import IAuthenticationEvents >>> from dolmen.authentication import IAuthenticationAPI >>> IAuthenticationAPI.isOrExtends(IAuthenticationInterfaces) True >>> IAuthenticationAPI.isOrExtends(IAuthenticationEvents) True >>> from zope.interface.verify import verifyObject >>> verifyObject(IAuthenticationAPI, dolmen.authentication) True
Descriptive interfaces
dolmen.authentication provides a set of base interfaces that can be used to normalize an authentication system:
>>> print IAuthenticationInterfaces.__doc__ This interface describes and exposes the meaningful interfaces of the authentication module. >>> interfaceDescription(IAuthenticationInterfaces) IPrincipalFolder: A container specialized in storing principal representations. IAccountStatus: Abstraction component allowing to check the status of a principal. IPrincipal: A principal representation, directly inheriting from zope.security IPrincipal, but redefining several fields for a user-friendly form display. IGroup: A logical grouping of principals. This component is an IPrincipal itself. IPasswordProtected: This interface defines any component protected by a password IPasswordChecker: Abstraction component in charge of resolving a principal'scredentials. >>> IAuthenticationInterfaces.providedBy(dolmen.authentication.interfaces) True >>> verifyObject(IAuthenticationInterfaces, dolmen.authentication.interfaces) True
Events interfaces and implementations
dolmen.authentication provides a set of basic events that can be used and declined, in order to handle and trace principals’ lifecycles:
>>> print IAuthenticationEvents.__doc__ This interface describes and exposes the meaningful events descriptions and components of the authentication module. >>> interfaceDescription(IAuthenticationEvents) IUserLoggedOutEvent: IObjectEvent extending event : a user has logged out. IUserLoggedInEvent: IObjectEvent extending event : a user has logged in. UserLogoutEvent: An IUserLoggedOutEvent implementation. UserLoginEvent: An IUserLoggedInEvent implementation. >>> IAuthenticationEvents.providedBy(dolmen.authentication.events) True >>> verifyObject(IAuthenticationEvents, dolmen.authentication.events) True
Changes
0.3 (2012-01-17)
Updates on code to fit last changes in the Dolmen/Grok stack.
0.2 (2010-05-29)
the LocatablePrincipalInfo adapter now implements _and_ provides the IPrincipalInfo interface. This allows the adapter to be used in the AuthenticatedPrincipalFactory adaptation.
0.1 (2010-03-26)
Initial release.
Metadata
Release files for dolmen.authentication 0.3
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 |
|---|---|---|---|---|
| dolmen.authentication-0.3.tar.gz | 6.0 kB | Without provenance | Details for dolmen.authentication-0.3.tar.gz |
Release files / dolmen.authentication-0.3.tar.gz
| Download URL | dolmen.authentication-0.3.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3c1387f6a19f026686a8de524634e300fb5b644180ebdfd464d628c4d7f3e8b3
|
|
BLAKE2b-256 checksum How to use checksums |
e8d6fac60527b4a3000901f464a1158533f84e8bcce07c5445792b94ccabbafb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for dolmen.authentication 0.3
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.