Also, make sure the "sessions" folder is either A) Symlinked to each other
application or B) Store sessions in database or in a cookie.
--
Thadeus
On Wed, Jan 26, 2011 at 9:38 AM, ron_m wrote:
> Also check this setting originally in db.py of the scaffolding app
>
> auth.settings.hmac_key = '
Also check this setting originally in db.py of the scaffolding app
auth.settings.hmac_key = 'sha512:.'
If you want to share the table across apps or migrate copies of the auth_xxx
tables, the code that generates the encrypted passwords use this as the
method and key.
>From http://web2py.com/book/default/chapter/04#Cooperation :
"Applications can connect to the same database and thus share tables.
It is not necessary that all tables in the database are defined by all
applications, but they must be defined by those applications that use
them. All applications t
There's also the Central Authentication Service:
http://web2py.com/book/default/chapter/08#Central-Authentication-Service
Says it doesn't work with Auth, but "this will change in the future." I
don't know what the status of that is. Massimo?
On Wednesday, January 26, 2011 12:32:35 AM UTC-5,
I don't know if this works. But how about 1 app for authorization
exclusively. And those two apps do not deal with authorization at
all. Then in each of the two apps, you simply use the database from
the app that deals with authorization exclusively.
5 matches
Mail list logo
