Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EC59A10E80 for ; Fri, 31 Jan 2014 17:52:32 +0000 (UTC) Received: (qmail 38678 invoked by uid 500); 31 Jan 2014 17:52:32 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 38640 invoked by uid 500); 31 Jan 2014 17:52:32 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 38633 invoked by uid 99); 31 Jan 2014 17:52:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jan 2014 17:52:31 +0000 X-ASF-Spam-Status: No, hits=2.5 required=5.0 tests=FREEMAIL_REPLY,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of swsachith@gmail.com designates 209.85.213.180 as permitted sender) Received: from [209.85.213.180] (HELO mail-ig0-f180.google.com) (209.85.213.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jan 2014 17:52:25 +0000 Received: by mail-ig0-f180.google.com with SMTP id m12so9925607iga.1 for ; Fri, 31 Jan 2014 09:52:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=j5Hy/pXpXHQaWD6XeCgwH/x/yVgh8RawJnEe7srUObQ=; b=v7GvDSVWoa4GhclK0ShtwixNdTqehJMJYw9xuWUPkK8Ye20h052X8b19VYXdtZF6BC 45zxAPi562nK6NUMKt4slf5VFRIsAt32mid7gAkhDiVuPcmL/cGKRk0FUrPTQkoh2Ftt z1EUXudFjfqmvrFSIZYzQr7CyCM/aYgV3Gc6gkWFdz9s/h5UATwSehwbFA2YqScgmi1U ZIZ+8UEcEeC745zMvxDxvapwMMqx+yOdDNfFqm+NJZi9MegmyOgm8V7UQpf0FTFsv14a ZCWd3M+Uc/1lH00Xjmso+m0Fy1FAJI3NnY2StODYg7/2TbEp8d6HdH/i/4m3VDRFWzSq 7Shg== MIME-Version: 1.0 X-Received: by 10.42.228.65 with SMTP id jd1mr1816795icb.62.1391190724422; Fri, 31 Jan 2014 09:52:04 -0800 (PST) Received: by 10.42.229.71 with HTTP; Fri, 31 Jan 2014 09:52:04 -0800 (PST) In-Reply-To: References: Date: Fri, 31 Jan 2014 12:52:04 -0500 Message-ID: Subject: Re: Users and UserGroups in Science Gateways From: Sachith Withana To: dev@airavata.apache.org Content-Type: multipart/alternative; boundary=001a1132e4ccf1b16a04f147d42f X-Virus-Checked: Checked by ClamAV on apache.org --001a1132e4ccf1b16a04f147d42f Content-Type: text/plain; charset=ISO-8859-1 As an end user, I think even with just a single tool, the argument for a group is there. As Saminda suggested, one may wish to have a join area to work in with a group, and individual work you aren't ready to share, even with just a single tool. Because a Gateway is wide open, it is easy to imagine a case where there are several groups, each with (potentially overlapping) users, who all are working with Amber for different projects.. I too forgot about the different project scenario. I agree with all the suggestions brought up by Mark and Saminda. Thanks a lot for the input. The gateway itself have to manage the users and userGroups. I will look into more usecases to figure out the best way to implement it. On Fri, Jan 31, 2014 at 12:44 PM, Saminda Wijeratne wrote: > > > > On Fri, Jan 31, 2014 at 9:28 AM, Miller, Mark wrote: > >> As an end user, I think even with just a single tool, the argument for >> a group is there. >> >> As Saminda suggested, one may wish to have a join area to work in with a >> group, and individual work you aren't ready to share, even with just a >> single tool. >> >> >> >> Because a Gateway is wide open, it is easy to imagine a case where there >> are several groups, each with (potentially overlapping) users, who all are >> working with Amber for different projects.. >> > Agreed. I totally forgot about shared projects scenario. Thanks for > pointing it out Mark. > >> >> >> Mark >> >> >> >> *From:* Saminda Wijeratne [mailto:samindaw@gmail.com] >> *Sent:* Friday, January 31, 2014 9:11 AM >> *To:* dev >> *Subject:* Re: Users and UserGroups in Science Gateways >> >> >> >> I'm not an expert on the Amber usecase, but I suppose it is possible to >> have multiple user groups for a single usecase. It could be to have a >> shared space of data hidden from each user group. It could be to author >> access/privilledges to the portal or resources depending on the user group. >> >> I would assume the mapping of user to usergroups would be many to one >> mapping. Unlike user roles I don't think it is sensible to have users being >> mapped to multiple groups (there is a whole area of security to consider >> here). >> >> >> >> (I do have to note that usergroup IMO is not a must concept for a science >> gateway) >> >> >> >> On Fri, Jan 31, 2014 at 8:55 AM, Sachith Withana >> wrote: >> >> Hi all, >> >> >> >> Can someone explain to me the mapping of users to groups in a Science >> Gateway? ( This is regarding the Amber usecase). >> >> >> >> Can there be multiple user groups in a gateway portal when it comes to >> just one usecase? >> >> ex: If we have only one usecase for the portal ( such as Amber) >> >> >> >> -- >> >> Thanks, >> >> Sachith Withana >> >> >> > > -- Thanks, Sachith Withana --001a1132e4ccf1b16a04f147d42f Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
As an end user, I think even with just a sing= le tool, the argument for a group is there.

As Saminda suggested, one may wish to have a join area to work in w= ith a group, and individual work you aren’t ready to share, even with= just a single tool.

 

Because a Gateway is wide open, it is easy to imagine a case where = there are several groups, each with (potentially overlapping) users, who al= l are working with Amber for different projects..


I too fo= rgot about the different project scenario. 
I agree with all the suggestions brought up by Mark and Saminda. Thanks a l= ot for the input. 


The gateway itself have to manage the users and userGroups. I will lo= ok into more usecases to figure out the best way to implement it. 



<= br>
On Fri, Jan 31, 2014 at 12:44 PM, Saminda Wij= eratne <samindaw@gmail.com> wrote:



On Fri, Jan 31, 20= 14 at 9:28 AM, Miller, Mark <mmiller@sdsc.edu> wrote:

As an end user, I think e= ven with just a single tool, the argument for a group is there.

As Saminda suggested, one= may wish to have a join area to work in with a group, and individual work = you aren’t ready to share, even with just a single tool.

 

Because a Gateway is wide= open, it is easy to imagine a case where there are several groups, each wi= th (potentially overlapping) users, who all are working with Amber for different projects..

Agreed. I totally forgot about shared projects scenario. Thanks for= pointing it out Mark. 

 

Mark=

 

From: Saminda = Wijeratne [mailto:s= amindaw@gmail.com]
Sent: Friday, January 31, 2014 9:11 AM
To: dev
Subject: Re: Users and UserGroups in Science Gateways<= /span>

 

I'm not an expert= on the Amber usecase, but I suppose it is possible to have multiple user g= roups for a single usecase. It could be to have a shared space of data hidd= en from each user group. It could be to author access/privilledges to the portal or resources depending on the use= r group.

I would assume the mapping of user to usergroups wou= ld be many to one mapping. Unlike user roles I don't think it is sensib= le to have users being mapped to multiple groups (there is a whole area of = security to consider here).

 

(I do have to note that usergroup IMO is not a must = concept for a science gateway)

 <= /p>

On Fri, Jan 31, 2014 at 8:55 AM, Sachith Withana <= ;swsachith@gmail.c= om> wrote:

Hi all,

 

Can someone explain to me the mapping of users to gr= oups in a Science Gateway? ( This is regarding the Amber usecase).

 

Can there be multiple user groups in a gateway porta= l when it comes to just one usecase?

ex: If we have only one usecase for the portal ( suc= h as Amber)

 

--

Thanks,

Sachith Withana=

 





--
Thanks,
=
Sachith Withana

--001a1132e4ccf1b16a04f147d42f--