Introduction
pyramid_cas allows your application to authenticate against a Jasig CAS server. It takes borrowed concepts from different packages like django.cas, anz.client, and collective.cas.
License
pyramid_cas is licensed under the Apache License 2.0.
Installation
pip install pyramid_cas
Instructions
Required:
Include pyramid_cas under pyramid.includes directive in your .ini file like this:
pyramid.includes = [... other packages ...] pyramid_casSet the cas server that will be used for authentication:
pyramid_cas.cas_server = your-cas-server pyramid_cas.redirect_route - allows you to specify what route name to redirect to after succesful authenticationOptional:
pyramid_cas.callback.get_user - allows you to use a callback function to store a different User object after CAS authentication. By default pyramid_cas will store (using the pyramid remember method) only the user id returned by CAS.Example:
pyramid_cas.callback.get_user = adminsite.security.getUserObject pyramid_cas.redirect_route = profile # redirects to profile page on successful authenticationUse the following route names for login and logout in your application:
cas-login cas-logout
TODO
Implement CAS 1.0 protocol
Add login and logout by injection and makes it configurable using tweens
Add tests
Add demos
Prevent adding pyramid_cas without settings
Add came_from parameter
0.4 [2/14/23]
Fix a python 3 import error
0.3 [7/21/14]
Now Apache licensed
Login and logout routes are now named
Added redirect route after successful authentication
0.2 [6/17/14]
Brought into compliance with PEP8
Clarified documentation
Fixed bug related to iteration over headers (thanks, Szymon: https://github.com/zefciu/pyramid_cas/commit/3b67e69ea2418e64fcf8312e00fa17e10198788f)
0.1 alpha
[April 13, 2012] Initial version
Metadata
Release files for pyramid-cas 0.4
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 |
|---|---|---|---|---|
| pyramid_cas-0.4.tar.gz | 7.0 kB | Without provenance | Details for pyramid_cas-0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyramid_cas-0.4-py3-none-any.whl | Python 3 | none | any | Details for pyramid_cas-0.4-py3-none-any.whl |
Total release size: 13.8 kB
Release files / pyramid_cas-0.4.tar.gz
| Download URL | pyramid_cas-0.4.tar.gz |
|---|---|
| Size | 7.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
140c7f133d005b249babc586300b0c097e339bf0c24ebd1922939efcf40f09ec
|
|
BLAKE2b-256 checksum How to use checksums |
3ec59d75680141ab2e2daac522b69ce125e6ee4fc5590bf5ae3e7af178f238db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Release files / pyramid_cas-0.4-py3-none-any.whl
| Download URL | pyramid_cas-0.4-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e3df6cd398d36d6c2c2ecdc7fd2368bd204c7449ae2e614a2a5b8fc85804cd8a
|
|
BLAKE2b-256 checksum How to use checksums |
8398fff04b6a14b0a32f7045b8aed236fb6c752142e8989403c3bce5ce234edf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.6
|
Security for pyramid-cas 0.4
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.