|
Monday 12 October 2009 8:43:53 am
Hello Ahel, We've recently done a similar thing, but for another piece of software - IP.Board - and in reverse direction - eZ Publish being the king of the installation, serving as an single sign on solution. For several reasons that architecture fit our needs better. In any way, we created an eZ Publish login handler and couple of hacks for registration/activation routines, and we call IP.Board API directly from eZ Publish (which by the way seems heavens better than vBulletin's, but that's just our opinion). This way the API does everything as it should be done (basically setting up the session for the forum software without having to access it or login into it right away), and also it has been planned for external integrations so there's this workflow which causes to create a fully functional forum user the moment he first accesses the forum application.
The rationale behind the chosen solution was:
- Only needed one siteaccess to one forum arrangements, no multiple languages (in our solution they have to share the domain, with forum being a subdirectory of eZ installation),
- We aimed at forums working around content rather than content being added to the forum,
- We have much more expertise with eZ Publish and therefore have more control over the integration than we would have trying to have forum application as a central part. Of course a more flexible approach could be to for example use openID, which is by default supported in IP.Board and there are some extensions for that for eZ Publish, if you go though the projects section. Hope this helps to boost a discussion around this interesting topic.
Cheers,
Piotrek
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|
