Re: [rfc] permissions managment

Am Wed, 14 Aug 2002 10:55:43 +0800 schrieb Alan Knowles <alan@akbkhome.com>: > What I would say is unneccessay : > HTML login pages: = why assume authentication is always going to be > web based - this is part of the applications responsibility.. +1 > Sessions := 50/50 if it should be generalized - I use a session > ->object var mapper.. - not that fussed if it stays similar to current > Auth, how ever would really prefer the use of > PEAR::getStaticProperty('Auth','store'); rather than Globals.. I don´t quite understand what you mean here... can you describe in more detail what your session->object var mapper does? > All of the 'Permissions/Group' management is outside the Auth > responsibility. - The question really goes what would be a standard > interface for the 'person' object. DB_DataObject Provides a good basis > for me, however, As long as a 'User' interface could be standardized - > you could easily implement wrappers to almost any user database/storage > scheme. LiveUser allows you to write your own backend classes that can retrieve user data from any kind of data source you want. The LoginManager class that you use in applications doesn´t need to know how the data is actually stored. > the authentication / user stuff should really just be a wrapper for > other applications User management systems.... > -- In the stuff I do, the person/user data table, grows and shrinks > depending on what the project requires, generally the only implication > of this is modifying the template, doing the ALTER TABLE..., and > running the DB_DataObject generator.. In the past, I´ve always had a generalized users table which contained data on all users who were allowed to login in any form. This table always contains only the data necessary for the login process itself (well, and there are of course the permission tables that are referencing the user table). All profile data, such as ie. adress, gender, credit card numbers and the like is stored in one or more separate tables that may change from application to application. If a person that has a profile also has an online account, its ID in the user table is just referenced in the profile table. I really don´t see the need to change the user table for each application - it should be used to store always the same kind of data. Regards, Markus -- *21st Media* | Consulting, Konzeption, Produktion für die Bereiche: Markus Wolff | Internet, Intranet, eCommerce, Content Management, Hamburg,Germany | Softwareentwicklung, 3D-Animation, Videostreaming http://21st.de | Tel. [+49](0)40/6887949-0, Fax: [+49](0)40/6887949-1