for the users db, you hust need to use the same jdbc url for archiva et Continuum users databases in datasources.
I don't remember how to configure the shared path for cookies. Brett, do you know? If you don't set it, you'll need to authenticate on both instead of only one login. Emmanuel On Tue, Jun 24, 2008 at 4:13 PM, Lustig, Marc (Allianz Deutschland, externer Mitarbeiter) <[EMAIL PROTECTED]> wrote: > that's interesting. is it documented somewhere? > > > -----Ursprüngliche Nachricht----- > Von: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 24. Juni 2008 14:49 > An: [email protected] > Betreff: Re: SSO Archiva / Continuum > > Archiva and Continuum can already work with the same db, it is what lot of > users already use in production. > > Emmanuel > > On Tue, Jun 24, 2008 at 2:18 PM, Lustig, Marc (Allianz Deutschland, > externer > Mitarbeiter) <[EMAIL PROTECTED]> wrote: > > > hi, > > since Archiva and Continuum are highly complimentary it would be helpful > > for many users to have a single login for both apps. I have heard this > > request a number of times! > > Already both apps ground on the same authentication and authoriation > system > > (redback) and the db schemas are also the same. > > Would it be possible to use a single db-instance for both apps? > > I suppose it won't work because the security-roles are different for each > > system. > > So, my idea is to leave the authorization each in the dedicated tables, > > while having the authentication at a central place/table. > > > > Can one of the Redback-developers please explain if it would be > sufficient > > to have a single table JDOUSER, and the rest of the tables to have one > for > > each app. I think the easiest way would be to use the same db-instance, > and > > simply prefix the table-sets: CONT_SECURITY_.... ARCH_SECURITY_.... > > > > I think anyway some better integration of Continuum and Archiva would be > > highly welcome. > > > > M. > > >
