On Fri, Jan 31, 2014 at 9:19 AM, Sachith Withana <[email protected]>wrote:

> Thanks a lot Saminda,
>
> So a user will have access to multiple shared spaces ( for each usergroup)
> and to his/her own private space.
>
> In the CIPRES usecase, how would you allow access to shared spaces in
> terms of the user experience?
> having one shared Space for the user and populate with all the experiments
> shared with the user or
> having multiple shared spaces categorized by the usergroup?
>
Unfortunately Airavata is still at its infant stage when managing users and
its groups. We do have the published space (shared among users in a
gateway) and user private space. We need to figure-out a good design and
architecture for managing user groups. But IMO this is more of a gateway
side feature rather than a middleware-resource-management goal.

>
>
>
> On Fri, Jan 31, 2014 at 12:11 PM, Saminda Wijeratne <[email protected]>wrote:
>
>> 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 <[email protected]>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
>
>

Reply via email to