Products.CAS4PAS
Products.CAS4PAS is the eggified version of CAS4PAS,an implementation of the CAS single-signon for Zope corps Pluggable Authentication Service.
To Do
In serious needs of tests and documentation.
Contributors
Lennart Regebro (regebro@gmail.com) - Original developer
Alexandre Sauv?? (mr.lex@free.fr) - CAS2 implementation
Derek Richardson - eggification
Changelog
2.1.1 2011-09-13
Add a first Plone 4 compatibility [marshalium]
Improve the Plone 3 and Plone 4 compatibility [encolpe]
Add a first implementation of the CAS gateway mode [encolpe]
2.1 2010-05-03
Fixed to not create session for anonymous user requests. [deo]
Added the z3c.autoinclude entry point so this package is automatically loaded [edegoute]
2.0.1
Removed came_from check that was disruptive. [derek_richardson]
2.0
Included Alexandre Suaves’s widely used patch. [derek_richardson]
eggified to Products.CAS4PAS by derek_richardson
1.0
Initial release of CAS4PAS built by: lregebro at: 2007-10-20T15:32:36 SVN Tag: https://svn.plone.org/svn/collective/CAS4PAS/tags/1.0.0 Build from: https://svn.plone.org/svn/collective/CAS4PAS/trunk@52114
Metadata
Release files for Products.CAS4PAS 2.1.2
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 |
|---|---|---|---|---|
| Products.CAS4PAS-2.1.2.tar.gz | 11.2 kB | Without provenance | Details for Products.CAS4PAS-2.1.2.tar.gz |
Release files / Products.CAS4PAS-2.1.2.tar.gz
| Download URL | Products.CAS4PAS-2.1.2.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
98be71a4b8fc30f73d181cf7fbad2dcd2976c2b7d2ab97d5e9b3a5c05097f5f7
|
|
BLAKE2b-256 checksum How to use checksums |
177715c6fac3f16b125989bd3d4e0be4e046da9f328cd2d08ec2b2202dd0d9d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.CAS4PAS 2.1.2
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.