[Typo3-dev] user management logic

[Wolfgang Klinger]

 *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... ,-)

 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...


 bye
 Wolfgang