airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Marru (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2710) How to assign owner of "everyone" group in Sharing Registry?
Date Fri, 06 Apr 2018 11:10:00 GMT


Suresh Marru commented on AIRAVATA-2710:

[~marcuschristie] I do not have any deep thoughts to add. But i am wondering if we step back
and think, shouldn't there be a simpler way of support sharing with PUBLIC and AUTHENTICATED_USERS 
within the sharing registry? I remember the discussion for everyone groups, but for all reasons
you mention, I feel we will over-engineer this and may be fundamentally re-thinking on this
now might save us from corner cases tomorrow. Just an idle thought. 

> How to assign owner of "everyone" group in Sharing Registry?
> ------------------------------------------------------------
>                 Key: AIRAVATA-2710
>                 URL:
>             Project: Airavata
>          Issue Type: Bug
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
> in AIRAVATA-2662 the "everyone" group is being added to the Sharing Registry.  A UserGroup
in the Sharing Registry must have a owner. This presents a problem, the "everyone" group cannot
be created until there is a user who can be the owner, but createUser should add each user
to the "everyone" group.
> For now the implementation of createUser creates the "everyone" group if it doesn't already
exist and makes this user the owner of the group.  That's less than ideal since the first
user of a domain ends up the owner of the "everyone" group.
> Here are some possible alternatives:
> * create a dummy admin user for the domain that is made the owner of the everyone group
> * allow groups to not have an owner (make the OWNER_ID column nullable on USER_GROUP)

This message was sent by Atlassian JIRA

View raw message