[Typo3-dev] user management logic

[Leendert Brouwer [Netcreators]]

"Wolfgang Klinger" <wolfgang at stufenlos.net> wrote in message
news:mailman.1809.1082643240.241.typo3-dev at lists.netfielders.de...
> *hiya!*
> On 15:16 Thu 22 Apr     , Leendert Brouwer [Netcreators] wrote:
> > Right, but where in the code is e.g. adding users happening currently?
> > Because I want to extend those parts of the Typo3 core, thus I need to
> > override those methods when subclassing the core classes. The generic
nature
> > of Typo3 makes it a little harder to just grep the code for e.g. insert
> > queries on the fe_users table.
>
>  As said before you won't find it, because it's nothing special and thus
>  provided by the default Typo3 data handler/interface/whatever...
>  In fact there are no methods you can override!
>  It's just another configuration.
>
>  You are dead-on, it's the generic nature of Typo3 ;-)

Having thought about this a bit more, this problem looks like something a
lot of people will run into. Because Typo3 will be a site's main framework
in a lot of cases, ideally everything in the website will be able to
integrate with Typo3. A lot of things that should be integrated have their
own user management. Take phpBB, moodle, phprojekt etc. for example. I can
imagine that most Typo3 implementors want to keep their userbase global and
transparent. Meaning, there should be one user that is able to log on to any
service inside the website as long as the service runs as a Typo3 extension
(so not a seperate user for every service). This _would_ be possible if
there were hooks in Typo3 for user management. If there were specialized
methods you could override (like an addUser() method for example), this
process would be much easier. Of course, generic is good, and most of the
generic nature of Typo3 is very flexible. That's awesome. But here, maybe
we'll have to wonder what exactly "generic" means. In order to be even more
generic in the sense of "it should be a transparent process to extend Typo3
with other services, keeping the userbase in one place", then having
explicit methods/hooks for user management could be seen as "more generic".
Does anyone have any thoughts on this? I'll be glad to clarify if the above
ramblings didn't make sense.


>
>  bye
>  Wolfgang
>
>
>