[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
================
Pyramid Cubicweb is an attempt to rebase the CubicWeb_ framework on pyramid.
It can be used in two different ways:
- Within CubicWeb, through the 'pyramid' cube and the
:ref:`pyramid command <cubicweb-ctl_pyramid>`.
In this mode, the Pyramid CubicWeb replaces some parts of
CubicWeb and make the pyramid api available to the cubes.
- Within a pyramid application, it provides easy access to a CubicWeb
instance and registry.
Narrative Documentation
=======================
.. toctree::
:maxdepth: 2
narr/quickstart
narr/ctl
narr/settings
narr/profiling
Api Documentation
=================
.. toctree::
:maxdepth: 2
:glob:
api
Change History
==============
.. toctree::
:maxdepth: 1
changes
Indices and tables
==================
* :ref:`genindex`
* :ref:`modindex`
* :ref:`search`
.. _CubicWeb: http://www.cubicweb.org/