[auth] Use a second authtkt policy for 'rememberme'
The former solution was buggy because the expire time of the auth cookie, if
set through 'remember', was lost on the first cookie reissuing.
The new approach, make possible thanks to multiauth, use two different cookies.
One for session bounded authentication (no 'rememberme'), and one for long
lasting authentication (w 'rememberme').
The choice between the two of them is done by adding a 'persistent' argument
to the top-level 'security.remember' call. Passing this argument will inhibate
a policy or the other.
The two policies are (a little) configurable through the
'cubicweb.auth.authtkt.[session|persistent].*' variables.
Related to #4985962
Source: pyramid-cubicweb
Section: python
Priority: optional
Build-Depends:
python,
python-setuptools,
python-pyramid,
python-waitress,
debhelper (>= 9),
Standards-Version: 3.9.6
Maintainer: Julien Cristau <julien.cristau@logilab.fr>
Homepage: https://www.cubicweb.org/project/pyramid-cubicweb
Vcs-Browser: http://hg.logilab.org/master/pyramid_cubicweb
Vcs-Hg: http://hg.logilab.org/master/pyramid_cubicweb
Package: pyramid-cubicweb
Architecture: all
Depends:
${misc:Depends},
${python:Depends},
python-pyramid (>= 1.5.0),
python-waitress (>= 0.8.9),
cubicweb-common (>= 3.19.3),
# XXX wsgicors?
Description: Integrate CubicWeb with a Pyramid application
Provides pyramid extensions to load a CubicWeb instance and serve it through
the pyramid stack.
.
It prefigures what CubicWeb 4.0 will be.