If the joomla system sets an sso cookie whose scope is for the entire domain, then I guess you could write an isis authenticator that would pick up this cookie and pass it to an sso verification service that would check that the cookie details have not been forged and then return the corresponding user id.
The system I'm working on in my day job at the moment does something similar to this. Dan Sorry to be brief, sent from my phone On Oct 19, 2011 4:05 PM, "Robert Matthews" <[email protected]> wrote: > Kevin > > I can't quite get my head around this. As the two systems are running > independently, how are you going to get the id/token from one to the other? > > Isis is capable of starting up without authenticating the user - see the > uses of ExplorationSession and AnonymousSession in the DnD and Scimpi UIs > respectively. The sessions there are set up during startup, for the DnD > viewer, and at the beginning of each request for Scimpi. > > What user interface are you considering using? > > Regards > Rob > > > On 17/10/11 17:24, Kevin Meyer - KMZ wrote: > >> Hi Robert, >> >> Indeed - I have already added a SQL authenticator to the Isis >> framework that can be used to verify details (login name and >> password), but I was now wondering about using session data so that, >> having logged into either Isis or Joomla, visiting the *other* framework >> would not require another login. >> >> Regards, >> Kevin >> >> >> On 17 Oct 2011 at 17:01, Robert Matthews wrote: >> >> Hi Kevin >>> >>> Authentication and authorisation in Isis is done via a couple of >>> plug-ins. So creating your own versions that check with Joomla's >>> security data is what I would look at first. >>> >>> Extend PasswordRequestAuthenticatorAb**stract to authenticate a user via >>> the database and extend AuthenticationManagerStandardI**nstallerAbstract >>> to install your authenticator. Add an isis.authentication property to >>> the isis.properties file to specify the installer class. >>> >>> Regards >>> Rob >>> >>> >>> >>> On 17/10/11 10:52, Kevin Meyer - KMZ wrote: >>> >>>> Dear all, >>>> >>>> I am working on another project that is being implemented on both Isis >>>> and Joomla!. Its for an institute that wants to provide CMS >>>> functionality >>>> for members (personal web pages, blogging, articles, etc), and also >>>> provide online user management (the backend) for the institute council >>>> (member enrolment, payment status, invoicing, etc). >>>> >>>> I'm using Joomla! 1.7 for the front-end, and Isis for the backend, >>>> sharing data via the SQL objectstore (common schema pattern, I >>>> guess). >>>> >>>> My question is: Would it be possible for a login on the CMS (Joomla!) >>>> to carry over onto the HTML viewer? I'll be looking into cookie-based >>>> sessions late today... >>>> >>>> Since, I think, Joomla uses session data stored in one of its tables, it >>>> might be easier to drive the login from the Isis direction instead (and >>>> have Isis create the session database information).. >>>> >>>> Regards, >>>> Kevin >>>> >>>
