[Typo3-dev] user management logic

[Leendert Brouwer [Netcreators]]

"Leendert Brouwer [Netcreators]" <leendert at netcreators.nl> wrote in message
news:mailman.1.1082707490.29191.typo3-dev at lists.netfielders.de...
>
> "Wolfgang Klinger" <wolfgang at stufenlos.net> wrote in message
> news:mailman.1934.1082706550.241.typo3-dev at lists.netfielders.de...
> >
> >  *hiya!*
> > On 09:28 Fri 23 Apr     , Leendert Brouwer [Netcreators] wrote:
> > > (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.
> >
> >  That's where "Services" jump in.
> >
> >  There's already a simple example for user authentication in this
> >  document:
> >
>
http://typo3.org/doc.0.html?&encryptionKey=&tx_extrepmgm_pi1[extUid]=1316&cHash=a691a1e9bd
> >
> >  I don't know if there is any actual development concerning user
> >  authentication with services, but it's the way to go...
> >  Maybe you can provide a proof of concept.
> >
> >  Read again what I answered on your first post... ,-)
>
> Got it! I initially thought these services was an idea that was not yet
> implemented. I'm going to read up on it and see what I can do with
services,
> and then I'll report on the experience :)
>
> >
> >  I think it's not necessary to insert all users into Typo3 if you can do
> >  it much easier (and cleaner) with service chains accessing different
> >  systems...
>
> True. But it might be tricky, as updating user information etc. should be
> done for all services in one place as well. Not sure if that will actually
> cause any trouble though, I'll experiment with it a bit. Thanks!

I suppose I'm not getting the services concept yet (only been working with
Typo3 for a few weeks now :)). I can see how services can be used to act as
filters, but I'm not exactly sure how to actually integrate third party
applications with Typo3 using services. For example, how would you integrate
phpBB with Typo3 using services (its user management system that is)?
Thanks.


>
>
> >
> >
> >  bye
> >  Wolfgang
> >
> >
> >
>
>