[Typo3-dev] Re: The future of typo3

[Didier Geheniau]

> -----Original Message-----
> From: typo3-dev-bounces at lists.netfielders.de 
> [mailto:typo3-dev-bounces at lists.netfielders.de] On Behalf Of 
> Daniel Hinderink [TYPO3]
> Sent: zondag 26 oktober 2003 23:54
> To: List for Core-/Extension development
> Subject: Re: [Typo3-dev] Re: The future of typo3
> 
> 
> Hi Didier,
> > 
> >>> Daniel Hinderi(n)k writes:
> >>> 
> >>>> On the general notion of creating a symbiotic frontend 
> and backend 
> >>>> user concept, I am less enthusiastic about this.
> >>>> 
> >>> I hope that this is not the way you understand what I have been 
> >>> writing. Of course it should be possible to separate those
> >> two parts
> >>> of the system. I just want what separates them to be 
> something more 
> >>> trivial rather than 938427 lines of PHP-code.
> >> 
> >> That is not the case, see below. I am however against a 
> unified user 
> >> concept in the sense of having e.g. One common table for reasons 
> >> already stated.
> >> 
> > 
> > Re-think the concept of authentication and authorization.
> > 
> > A user is one person, this person can access the front-end and the 
> > back-end. By login in with a user account he is 
> authenticated as the 
> > right person.
> > 
> > Groupmemeberships gif him the authorization to do things. 
> It doesn't 
> > matter if you split the backend and the frond end. You can always 
> > define backend groups with backend rights and frond end groups with 
> > front-end rights.
> > 
> > So keep user records simple, there are situations that 
> companies want 
> > to use or import users from an other environment.
> 
> That is probably right for content creation from an internal 
> user base, kept in Active Directory/eDirectory/LDAP. But 
> frontend users in real life business cases don't exist in the 
> formats mentioned above. They are kept in specialised 
> CRM-systematics. There is simply no business case to speak of 
> and on top of that a structural problem witn integrating 
> these two tables. In fact, I see no advantage to speak of in 
> any of your (plural) explanations.

It does not matter weather they exist on what system, the same person
can still be accessing the front and back-end. Personally I think
general user information should be kept in a LDAP like system so it can
easily accessed by other systems. A CRM system is something completely
deferent then an Active Directory,eDirectory or other LDAP. Also a
CRM-system can make use of LDAP. But that discussion goes on an other
level I think.

 
> > Personal user settings
> > can be stored in typo3. No authorization information must 
> be stored in 
> > a user record, store this information in the group records.
> 
> It doesn't work for content creation beyond simple setups and 
> any major vendor (coremedia, vignette ...) is not following this path.

That they doesn't follow this path might not be that it is not the right
path, but when they choose this path they did not see an other way.
Company choose systems for strategically reasons. And the best solution
is not the only strategy. I see many companies choosing for systems
because of other reasons then the best solutions!

Typo3 is a general system, and I hope not mentioned for just one ore to
companies and/or branches! Separation of front-end and back-end must not
be based on the techniques! You can implement one method where user
management (not the authorization, only the authentication) is done with
the same method. Splitting physical storage location of front-end and
back-end users can always be realised by an extra option and remaining
usage of the same technique!.

By using defend techniques for frond-end, back-end usage u choose by
design that it is impossible to merge them!
 
> Cheers
> 
> Daniel
> 
> > 
> > Regards,
> > 
> > Didier M.J.C. Gehéniau
> > Consultant
> > 
> > FEAS
> > info at feas.net
> > www.feas.net
> > 
> > 
> > _______________________________________________
> > Typo3-dev mailing list
> > Typo3-dev at lists.netfielders.de 
> > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-dev
> > 
> 
> -- 
> TYPO3 - get.content.right
> 
> Daniel Hinderink
> Marketing, Press Relations, Strategy
> http://www.typo3.com
> 
> 
> _______________________________________________
> Typo3-dev mailing list
> Typo3-dev at lists.netfielders.de 
> http://lists.netfielders.de/cgi-> bin/mailman/listinfo/typo3-dev
>