diff options
| author | Robert Buchholz <rbu@goodpoint.de> | 2014-03-03 16:24:31 +0100 |
|---|---|---|
| committer | Robert Buchholz <rbu@goodpoint.de> | 2014-03-03 16:30:05 +0100 |
| commit | 1bd3157143c7ae6e0a35fa07e4f0888ddd347ab5 (patch) | |
| tree | 4de39b2a6f41d09aac2a4f4835e5f4177231d1b5 /docs/quick_tutorial/view_classes | |
| parent | cf026e2cd8704a679dd83760907d8847deabb18e (diff) | |
| download | pyramid-1bd3157143c7ae6e0a35fa07e4f0888ddd347ab5.tar.gz pyramid-1bd3157143c7ae6e0a35fa07e4f0888ddd347ab5.tar.bz2 pyramid-1bd3157143c7ae6e0a35fa07e4f0888ddd347ab5.zip | |
Hand RepozeWho1AuthenticationPolicy.remember kwargs to repoze.who #1249
Documentation for pyramid.security.remember supports keyword arguments
to hand over to the authentication policy. However, when using
RepozeWho1AuthenticationPolicy, all of the kw were dropped in remember.
It is my understanding that with repoze.who, additional configuration
parameters shall be stored in the identity dictionary. In our case,
setting the max_age parameter to the authtkt identifier, would be done
using an identity {'repoze.who.userid':principal, 'max_age': 23}.
It seems sensible just to hand over kw through the identity dictionary
and all users to specify max_age or other parameters such as userdata.
Diffstat (limited to 'docs/quick_tutorial/view_classes')
0 files changed, 0 insertions, 0 deletions