[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
pyramid-cubicweb (0.2.1-1) unstable; urgency=medium
* upstream release
-- Christophe de Vienne <christophe@unlish.com> Fri, 23 Jan 2015 12:57:25 +0100
pyramid-cubicweb (0.2.0-1) unstable; urgency=medium
* upstream release
-- Christophe de Vienne <christophe@unlish.com> Wed, 21 Jan 2015 13:27:28 +0100
pyramid-cubicweb (0.1.3-1) unstable; urgency=medium
* upstream release
-- Christophe de Vienne <christophe@unlish.com> Mon, 08 Dec 2014 20:23:11 +0100
pyramid-cubicweb (0.1.2-1) unstable; urgency=medium
* upstream release
-- Christophe de Vienne <christophe@unlish.com> Sat, 15 Nov 2014 20:25:42 +0100
pyramid-cubicweb (0.1.1-1) unstable; urgency=medium
* upstream release
-- Christophe de Vienne <christophe@unlish.com> Sun, 02 Nov 2014 23:33:46 +0100
pyramid-cubicweb (0.1.0-1) unstable; urgency=low
* Initial release.
-- Julien Cristau <julien.cristau@logilab.fr> Mon, 06 Oct 2014 10:18:27 +0200