Return-Path: Delivered-To: apmail-continuum-dev-archive@www.apache.org Received: (qmail 20724 invoked from network); 25 Jun 2008 14:01:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 25 Jun 2008 14:01:27 -0000 Received: (qmail 69946 invoked by uid 500); 25 Jun 2008 14:01:28 -0000 Delivered-To: apmail-continuum-dev-archive@continuum.apache.org Received: (qmail 69919 invoked by uid 500); 25 Jun 2008 14:01:27 -0000 Mailing-List: contact dev-help@continuum.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@continuum.apache.org Delivered-To: mailing list dev@continuum.apache.org Received: (qmail 69908 invoked by uid 99); 25 Jun 2008 14:01:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 07:01:27 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [208.82.99.81] (HELO rectang.com) (208.82.99.81) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2008 14:00:37 +0000 Received: from Dito.lan (82-71-30-90.dsl.in-addr.zen.co.uk [82.71.30.90]) by rectang.com (Postfix) with ESMTP id 32D10534034 for ; Wed, 25 Jun 2008 15:00:55 +0100 (BST) Message-Id: <7D7E0B9E-9801-47F5-BF1C-7584D493EF73@handyande.co.uk> From: Andrew Williams To: dev@continuum.apache.org In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Subject: Re: SSO Archiva / Continuum Date: Wed, 25 Jun 2008 15:00:53 +0100 References: X-Mailer: Apple Mail (2.924) X-Virus-Checked: Checked by ClamAV on apache.org I had a project that integrated the two and used a single authentication source - see maven-enterprise in the maven sandbox. Sure it is well out of date now, but it might show you how to set it up. Hope it helps, Andy On 24 Jun 2008, at 13:18, Lustig, Marc (Allianz Deutschland, externer Mitarbeiter) 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.