Authentication modules for web servers, like Apache or IIS, are more plentiful than those for Zope and Plone. WebServerAuth lets you take advantage of these in your site: just configure your web server to authenticate the user and store his or her login name in a request header, and WebServerAuth will convince Plone that that user is logged in. WebServerAuth has been used with LDAP, Active Directory, Kerberos, Shibboleth, Pubcookie, and CoSign and should work with anything else that can put a username into a header.
Metadata
Release files for Products.WebServerAuth 1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distributions (sdists)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Products.WebServerAuth-1.7.zip | 35.5 kB | Without provenance | Details for Products.WebServerAuth-1.7.zip | |
| Products.WebServerAuth-1.7.tar.gz | 24.5 kB | Without provenance | Details for Products.WebServerAuth-1.7.tar.gz |
Release files / Products.WebServerAuth-1.7.zip
| Download URL | Products.WebServerAuth-1.7.zip |
|---|---|
| Size | 35.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a1165617b1f3e6791a88f90be873fbac4575a5e9b153b1d53f96cadc7f6ec260
|
|
BLAKE2b-256 checksum How to use checksums |
e40a8ed62e797b078c46bb9a5e7c63ec1b45b3052ef18f07062d3998d2025955
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / Products.WebServerAuth-1.7.tar.gz
| Download URL | Products.WebServerAuth-1.7.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79fbeb30539b1ed9bac76af1ac1c2ac2e917efc0c4999928c89e424d5c54a6e9
|
|
BLAKE2b-256 checksum How to use checksums |
5cb2ecac7e3cfe842f7e93cc2458c44bdca1941ab386fcd2a9ea84ea938a72d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.WebServerAuth 1.7
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.