RE: permUser information

> 
> yeah .. and sometimes its not feasible to modify the auth source, since
> its controlled by someone else or is part of a legacy database. i
> understand your problem.
> 
Thats exactly what i mean :)

> 
> I dont see us adding an information table.
> Also you can emulate the isactive and lastlogin stuff already using a
> postlogin observer.

I might just have discovered the true nature of the containers. Is it true
that one perm user can only be found in one exclusive container? In that
view your answer seems more satisfying to me because I always had the
thought that one perm_user could be authenticated in multiple ways using
multiple containers. But I realize that that's not true since perm_user_id
in the liveuser_perm_users table is a primary key.

It would not allow:
perm_user_id 	auth_user_id 	auth_container_name
1			12			'DB_Complex'
1			julien		'POP3'

So ONE perm_user could only be authenticated using ONE specific container? 

> The entire data structure of the permission container is extensible. You
> can add new fields, even add new tables. This part is not well
> documented and probably should get documented since its a very powerful
> feature. I have explained it in bit and pieces a few times on this list
> already, so if anyone could write up some docs it would be appreciated.

I will try to find it in the archive. By the way: the archive of this list
seems to be outdated a bit.
http://mailman.21st-hq.de/mailman/private/liveuser/

Regards,

Julien