1
Hi everyone,
I'd like to integrate a XOOPS forum with my existing web application which also uses user accounts and forces users to login.
I already migrated all existing user data to the XOOPS database (table xoops_user) so that all accounts are available in xoops. I was lucky that in my own user table passwords were encoded as md5-hashes like XOOPS does, too. So all existing passwords work fine in xoops.
I also built an observer mechanism which replicates all changes in my user data to xoops; it works really fine

---------------------------
The next step seems to be harder and that's the one I need your help for:
In my web application I want to offer a menu item which opens a new browser window with a XOOPS session. But the user (who has already logged in into my application correctly) should not have to login once more into xoops. I want him to get logged in into XOOPS by my application.
I think I have to write a new record to the xoops_session table before opening the XOOPS browser window, but is that enough?
Do I have to set some cookies? What about the different Urls of my web application and my XOOPS site?
Where can I find more information about that funny string in table xoops_session, column sess_data? I couldn't find the php script which creates that string. What info do I need to reproduce it?
I found a sort of XOOPS remote control called xml-rpc, intended for blogging interoperability. Could that be an alternative approach for me?
Did anyone here have a similar problem and solved it successfully?
Is my idea really feasable or am I destined to fail?
Thanks for any advices/opinions,
Perry