Hi Robert, > 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?
Indeed - this is precisely the problem. How to let the authentication from one be picked up by the other. The closest might be to see how Joomla! stores the user sessions (it creates a row in a session table). Ideally, I'd like for (one of) the systems to also create the required authentication/session information (cookie) for the other.. But this is probably not possible. > Isis is capable of starting up without authenticating the user - see the No, I do need authentication, I was hoping to "share" the authentication, though. > 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? I've never been able to get Scimpi to properly support contributed actions on the current entity (the curent entity always comes up as null when the contributed action is executed), so I'm using the HTML viewer. (I can't find my previous threads on this topic in the mail archive). It's no train smash if the user has to authentication for each application - they will rarely need to login to the Isis session (only the administrators need it, when new members are signed on, or to process financials, etc). Regards, Kevin > 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 PasswordRequestAuthenticatorAbstract to authenticate a user via > >> the database and extend AuthenticationManagerStandardInstallerAbstract > >> 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)..
