Please Log in to join the conversation.
Suggest looking into some multi-site extensions as perhaps they'll work with CB too. Aside from that you could try using CB Auto Actions with external queries to push users data to other databases.(1) Is there a ready made tool to do this?
Sure if you implement an oAuth usage for your Joomla site then implement the handling for such oAuth usage into CB Connect.(2) Is there a way to tweak CBconnect so that it can do this job?
We've plans to implement oAuth support in a future CB release, but I can't provide as to when this would be available.(3) If not, could you add this feature to CB connect?
Manually moving user rows from 1 database to another I suppose is another option. Maybe a CRON job can be done to do this.(4) If any, what other avenue should I pursue?
OpenSocial is gone in latest releases.(5) It seems that CBconnect makes use of OpenSocial. Is there a way for me to achieve my goals via OpenSocial. Do you have anything I could read to understand how to do this?
Please Log in to join the conversation.
Please Log in to join the conversation.
You'd have to create one or wait for one to become J3.0 ready in this case I suppose.(1) No extension exist that would span across multiple servers for J3.
Correct, only way for that to work is to also sync the session everytime the user logs in. You'd then need to create a cookie to link the session id to the user on the other sites. You may have cross domain problems in that regard.(4) A Cron Job would duplicate and sync the user data but it would not free users from having to log into each system as they navigate from one to another. Is this a correct assumption?
There's no other solution except to implement oAuth or develop some sort of Authentication plugin for Joomla that checks credentials against all your other sites then registers or logs in and syncs the data. That'd require some sort of RESTful API on your CB sites though to handle the response.(1) I am afraid that CB Auto Actions queries would add to the page load and that under heavy server use, the queries would fail and lead to inconsistencies (as I can already experience in another system). This is why a distinct SSO/SSI system would be better.
Massive work.(3) I will look into oAuth. Is implementing oAuth support a huge work?
Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.