Re: permUser information

Julien Hofstede wrote:

> But I must admit I think it's a little odd that a permUser always requires a
> DB or XML-Auth-Container to store user information. So when I decide to use
> LDAP as authentication I do need a DB or XML-Authentication-Container to
> store a first or lastname? 

No, since you cannot authenticate against one container and pull data 
from another one. In that case we would expect you to store that 
information inside the LDAP container.

> I know that user information isn't either really authentication information
> or permission information but thinking about it I think the user information
> would fit better at the perm_user table since it's a one-to-many relation
> [e.g. one perm user has many authentication methods]. 

But what if someone wants to store the last login time on a per auth 
container basis? I guess what you are driving at is that LiveUser wraps 
around existing auth sources and expects people to use the LiveUser 
storage structure only for permissions. However keep in mind that 
LiveUser makes permissions usage optional, but authentication is required.

It is currently possible to extend the perm_users table with any field 
(aside from is_active and last_login fields) and I can see us adding 
fetching of all of these fields into a property into the permission 
containers. Open a feature request so we can ponder this some more.

regards,
Lukas Smith
[email protected]
_______________________________
   BackendMedia
   www.backendmedia.com
   [email protected]

   Linn Zwoch Smith GbR
   Pariser Str. 44
   D-10707 Berlin

   Tel +49 30 83 22 50 00
   Fax +49 30 83 22 50 07