INTRO
-----

Plone by default uses GRUF. If you want to use default CookieCrubmbler 
you can just set mysqlUserFolder as described in Notes.GRUF. Note that this
method will store username and password in a session cookie.

mysqlUserFolder cookie mode offers some advantages compared to CookieCrumbler:
	- It never stores username/password in cookies. Cookies only contain
		generated random values which are compared against the database.

	- Because of the previous one, mysqlUserFolder can be configured to store
		user cookie as a permanent cookie, with specific "valid" time (which
		is checked against the database).

	- mysqlUserFolder will also keep track of sessions (using cookies). 
		Session "parameters" can be configured.

SETUP (FOR COOKIES)
-------------------

0) Patch GRUF (Only for Plone 2.0)
	The patch is needed for GRUF, since by default it never tries to 
	authenticate user if there is no user information present. But mysqlUF 
	stores it's info in a special cookie which is ignored by GRUF. Use
	plone/PLONE-GRUF.patch for this. Note that this patch doesn't change 
	anything special in GRUF, so there are no side efects.

1) Create mysqlUserFolder inside GRUF as user source. Configure it to use
	cookies.

2) Script: setAuthCookie ()
	Inside portal_skins/custom/ you have to create empty script 
	setAuthCookie (). This will prevent Cookie Crumbler to store user 
	information in it's cookie (by default it stores username and password).

3) Script: logout ()
	Inside portal_skins/custom/ create script "logout". This will override 
	standard plone logout script (from plone_scripts). This is necessery since
	plone won't delete mysqlUserFolder cookies. The example logout script can 
	be found in docs/plone/. For Plone 2.1 use logout-2.1.py

4) AUTO_CREATE_ROLES
	Turn AUTO_CREATE_ROLES in cfg.py to 1. This is needed for normal GRUF 
	operation.