Customizing SMF > Portals, Bridges, and Integrations

Typo3/SMF 2.0

<< < (2/2)

sootersong:
I'm also VERY interested in a solution to exactly this problem.

jack:
OK, I have basic user integration working now :)

What works :

User login :-
[*]A user can log into the Typo3 front end using their SMF credentials. The user is automatically logged into SMF also.
[*] Optional SSO : If a user is logged into SMF, Typo3 can pick this up and silently log them into The Typo3 Frontend.
[*] Optional SSO : The user is automatically logged out of SMF when they log out of typo3 frontend.
[*] If a typo3 frontend user account does not exist for the user, one is automatically created. A single Typo3 usergroup and storage folder for such users is configurable.
[*] Typo3 user's name is synchronised with SMF's membername.

Future plans :-
[*] Awareness of SMF groups.
[*] Backend authentication.
[*] Logout from SMF causes logout of Typo3 frontend (will likely require a mod for SMF)
[*] Documentation ;)

I have not tested what happens with banned or un-activated users yet. This depends on functionality within smf_api. I can't see any real mention of the banning or activation mechanism in the api, so my gut feeling is that such users will be allowed to log in but I'm not 100% sure.

I want to do some work on dealing with situations where SMF is not installed or mis-configured but otherwise could upload to TER today with the above (lack of) functionality if anyone's interested?

Navigation

[0] Message Index

[*] Previous page