[
https://issues.apache.org/jira/browse/AIRAVATA-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422733#comment-16422733
]
Eroma commented on AIRAVATA-2573:
---------------------------------
1. User deletion make sense for users who have got the initial account creation
issues (junk account, email is incorrect, never got the verification link,
etc...). accounts that never got either email verified or enabled. Deleting
these make sense.
2. What about user accounts that used the gateway, have experimental data? More
than deleting the account these accounts should be grouped meaningful to the
gateway admin. If the user was inactive for a defined X duration group them a
'Inactive'. If the user is blacklisted and admin doesn't want them to use the
gateway anymore group them as 'Blacklisted'. If user is enabled but never used
the gateway at least ones they can either fall to 'inactive' or 'blacklisted'
group. But any of these should be reversible by the gateway admin if decided to.
3. Another situation that got our attention is that when one gateway account
doesn't work users go on creating multiple accounts using he same email. This
again collects unused accounts in the gateway. In production gateways we should
restrict users creating multiple accounts using the same email. This will force
the user to get the account fixed contacting the gateway admin. But for ease of
testing the development and staging gateways should be able to create accounts
using same email. So we should have a way of enabling this feature at each
gateway level.
> Ability to delete users for gateway admins
> ------------------------------------------
>
> Key: AIRAVATA-2573
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2573
> Project: Airavata
> Issue Type: New Feature
> Components: PGA PHP Web Gateway
> Affects Versions: 0.18
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Major
> Fix For: 0.19
>
>
> In the gateway currently deleting users are not possible for gateway admins.
> A new requirement has come to have delete user feature implemented.
> Thi requirement is to delete abundant or unused usr accounts. Users will go
> on creating multiple accounts one after the other if they have login or
> access issues in the gateway. Gateway admins will be left to deal with
> multiple unused accounts from the same user in the gateway. At a scenario
> like this ability to delete the user accounts make sense. But from gateway
> development and implementation point of view there are much to consider. When
> deleting the user accounts do we;
> 1. Consider whether they are active in the gateway? meaning is the email been
> verified? have thye given a active role?
> 2. Have they submitted at least a single experiment? If so do we let the user
> to be deleted? What about his experimental data?
> 3. Have they created any projects?
> 4. Have they shared any data with others?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
