Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 67587 invoked from network); 7 Feb 2008 18:22:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2008 18:22:39 -0000 Received: (qmail 90869 invoked by uid 500); 7 Feb 2008 18:22:31 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 90819 invoked by uid 500); 7 Feb 2008 18:22:31 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 90808 invoked by uid 99); 7 Feb 2008 18:22:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 10:22:31 -0800 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jesse.mcconnell@gmail.com designates 64.233.170.188 as permitted sender) Received: from [64.233.170.188] (HELO rn-out-0910.google.com) (64.233.170.188) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Feb 2008 18:22:02 +0000 Received: by rn-out-0910.google.com with SMTP id e21so1555951rng.16 for ; Thu, 07 Feb 2008 10:21:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=4HD35Uup/tNkqx+/gKxfyydN8WLUX857EWDvBATurtY=; b=NUOBwtD92lyRhrCQsBziLyGmHQCq01V/7B0fMbTbZbWgjwZh3SpNF9vCkxOEX3VfmvKx/p2ylSgpsTf70P4PTuhbzAF4I2O3c1H/3eMEbUJFfwVycq/2WjVKMH0F1Kq6Ha28uDGUMcd5tPPzKVbSZ4fm614QlVWSuYbkPOEZdEg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=OJNhydvvzh1qexB5kFRds1spYd5bJJ7jWkOdZAMzldN4ZuZKl1mZ2L+hJ0N8gLANnyD9DC1GlpFeB02YYngZggLS/yROhjjcXRmtwCBfTEL+maasSxXNxXbRouZanIRQ5+jEYZ+QycOci1A+y+A4goYr7RRoknFEzlncYWdcqPA= Received: by 10.142.44.11 with SMTP id r11mr6441312wfr.102.1202408486693; Thu, 07 Feb 2008 10:21:26 -0800 (PST) Received: by 10.143.38.11 with HTTP; Thu, 7 Feb 2008 10:21:26 -0800 (PST) Message-ID: Date: Thu, 7 Feb 2008 12:21:26 -0600 From: "Jesse McConnell" Sender: jesse.mcconnell@gmail.com To: "Apache Directory Developers List" Subject: Re: Google Team Edition and Triplesec In-Reply-To: <47AB4A24.3090203@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_481_12783122.1202408486677" References: <47AB4A24.3090203@gmail.com> X-Google-Sender-Auth: 150ead8f78ff9897 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_481_12783122.1202408486677 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline oh goodie, I have been waiting/lurking for some triplesec material to crop up on this list since talking to david jencks at apachecon :) in general there seems to be a shortage of actual open source role based access control implementations so any offering in this regard is good for triplesec and apacheds...I am hoping to swap out the rbac implementation in redback (underlying user manglement solution in use for continuum and archiva in mavenlands) with something a little more standard and bullet proof. jesse On Feb 7, 2008 12:12 PM, Ole Ersoy wrote: > Hey Guys, > > I was just reading through this article: > > http://news.yahoo.com/s/nm/20080207/wr_nm/google_team_software_dc_1 > > and thought of triplesec. From 50K feet (OK maybe a little lower) it > sounds like Triplesec would be the ideal solution for managing (create, > read, write, execute, etc.) groups of collaborators working on different > documents. All the users could be stored in ADS, along with the locations > of user documents, and the users could then just assign permissions using > the role based hierarchy discussed. This seems to be a hot area for Google > Apps, and thus presumably others will follow suit, and if triplesec were > positioned as the right solution for this it could be good for all of ADS as > a whole. > > Cheers, > - Ole > > -- jesse mcconnell jesse.mcconnell@gmail.com ------=_Part_481_12783122.1202408486677 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline oh goodie, I have been waiting/lurking for some triplesec material to crop up on this list since talking to david jencks at apachecon :)

in general there seems to be a shortage of actual open source role based access control implementations so any offering in this regard is good for triplesec and apacheds...I am hoping to swap out the rbac implementation in redback (underlying user manglement solution in use for continuum and archiva in mavenlands) with something a little more standard and bullet proof.

jesse

On Feb 7, 2008 12:12 PM, Ole Ersoy <ole.ersoy@gmail.com> wrote:
Hey Guys,

I was just reading through this article:

http://news.yahoo.com/s/nm/20080207/wr_nm/google_team_software_dc_1

and thought of triplesec.  From 50K feet (OK maybe a little lower) it sounds like Triplesec would be the ideal solution for managing (create, read, write, execute, etc.) groups of collaborators working on different documents.  All the users could be stored in ADS, along with the locations of user documents, and the users could then just assign permissions using the role based hierarchy discussed.  This seems to be a hot area for Google Apps, and thus presumably others will follow suit, and if triplesec were positioned as the right solution for this it could be good for all of ADS as a whole.

Cheers,
- Ole




--
jesse mcconnell
jesse.mcconnell@gmail.com ------=_Part_481_12783122.1202408486677--