Package: collective - SessionCrumbler
Provides a session based login for userfolders.
a test of SfIndex product
Sourceforge Info
| Project Name: | collective |
| Package Name: | SessionCrumbler |
| Files Page: | http://sourceforge.net/project/showfiles.php?group_id=55262&package_id=111527 |
| Browse CVS: | http://cvs.sourceforge.net/viewcvs.py/collective/SessionCrumbler/ |
Releases
| Release Date | Release Name | Download | |
|---|---|---|---|
| 2004-03-04 15:00 | 0.1 | sourceforge |
Package README (CVS ver. 1.2)
SessionCrumbler
SessionCrumbler provides a session based login for userfolders which
does not support this. The SessionCrumbler implementation relies on the
CookieCrumbler from CMFCore and therefore requires CMFCore product. It
is meant to be used in a CMF/Plone or icoya site to provide logins which
can time out when the user hasnt done any action within a period of time.
Compared to CookieCrumbler the SessionCrumbler doesnt use a cookie to
store the authentication information, but stores the __ac part inside the
current users Zope session (REQUEST.SESSION).
1. Installation
Copy this product into you Zope instance's Products folder and restart
this instance. Afterwards open the ZMI and go into your portal folder.
Remove the cookie_authentication object (CookieCrumbler) and add a new
SessionCrumbler object with it session_authentication. The Session-
Crumbler provides the same properties as the CookieCrumbler. So change
their values if required.
NOTE: Only one crumbler can be installed into the same folder at the
same time. So you _have_ to remove the CookieCrumbler object before
adding a SessionCrumbler.
2. Usage
Usage is exactly the same as for the CookieCrumbler. You need a login
template which posts the required form keys (see properties) to your
portal. Only the user name is stored inside a cookie if possible. Any-
thing else is stored inside the session.
To configure the session timeout consult the zope session documentation
and visit /temp_folder/session_data inside the ZMI.
NOTE: The session timeout is reset on every restart of Zope.
To persistently configure the session timeout see the
"session-timeout-minutes" Directive inside your zope configuration
(zope.conf). This only applies for zope 2.7 or higher though.
ZEO Users:
Sessions are kept inside a ram based container which is not
shared among zeo clients. So if you are using multiple zeo
clients you need a single session folder. A quick solution
to get this can be found at http://www.zopelabs.com/cookbook/10612343-
37.
3. Enjoy
I hope you enjoy using this software. If you have any comments,
suggestions or would like to report a bug, send an email to the author:
Simon Eisenmann
simon@struktur.de
--
(c) 2004, struktur AG and contributors. All rights reserved.
visit: http://www.icoya.com