[
https://issues.apache.org/jira/browse/AIRAVATA-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16327260#comment-16327260
]
Eroma edited comment on AIRAVATA-2571 at 1/16/18 4:50 PM:
----------------------------------------------------------
Testing in [https://dev.seagrid.org|https://dev.seagrid.org/] and in
[https://scigap.org/] (as its already deployed in scigap production portal).
Test cases.
[https://dev.seagrid.org|https://dev.seagrid.org/]
# Create a new account, user enabled should be disabled ((x))- PASS
# New user verifies the email using the link, user enabled changes to enabled
((/)) - PASS
# New user clicks on a expired email verification link and gets 'Account
confirmation failed! We're sending another confirmation email. Please click the
link in the confirmation email that you should be receiving soon.'. User
enabled should remain in (x) - PASS
# New user gets role changes, given admin-read-only after email verified.
Should not have any impact on the user enabled. should remain in (/) - PASS
# Try to change user's role prior to email verification. Should not have any
impactand it will remain (x) until email verified. Check roles button is
disabled until email is verified. - PASS
# Give user-pending role to a user with an active role. User enabled will
remain as it ((/)) was since role changes has no impact on it. - PASS
[https://scigap.org/]
# Create a new account, user enabled should be disabled ((x))-
# New user verifies the email using the link, user enabled changes to enabled
((/)) -
# New user clicks on a expired email verification link and gets 'Account
confirmation failed! We're sending another confirmation email. Please click the
link in the confirmation email that you should be receiving soon.'. User
enabled should remain in (x) -
# New user gets role changes, given admin-read-only after email verified.
Should not have any impact on the user enabled. should remain in (/) -
# Try to change user's role prior to email verification. Should not have any
impactand it will remain (x) until email verified. Check roles button is
disabled until email is verified. -
# Give user-pending role to a user with an active role. User enabled will
remain as it ((/)) was since role changes has no impact on it. -
was (Author: eroma_a):
Testing in [https://dev.seagrid.org|https://dev.seagrid.org/] and in
[https://scigap.org/] (as its already deployed in scigap production portal).
Test cases.
[https://dev.seagrid.org|https://dev.seagrid.org/]
# Create a new account, user enabled should be disabled ((x))- PASS
# New user verifies the email using the link, user enabled changes to enabled
((/)) - PASS
# New user clicks on a expired email verification link and gets 'Account
confirmation failed! We're sending another confirmation email. Please click the
link in the confirmation email that you should be receiving soon.'. User
enabled should remain in (x) - PASS
# New user gets role changes, given admin-read-only after email verified.
Should not have any impact on the user enabled. should remain in (/) - PASS
# Try to change user's role prior to email verification. Should not have any
impactand it will remain (x) until email verified. Check roles button is
disabled until email is verified. - PASS
# Give user-pending role to a user with an active role. User enabled will
remain as it ((/)) was since role changes has no impact on it. - PASS
> Have 'user enabled' appear in Admin dashboard -->Users
> ------------------------------------------------------
>
> Key: AIRAVATA-2571
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2571
> Project: Airavata
> Issue Type: New Feature
> Components: PGA PHP Web Gateway
> Affects Versions: 0.18
> Reporter: Eroma
> Assignee: Neeraj Lad
> Priority: Major
> Fix For: 0.18
>
>
> Currently in Admin Dashboard --> Users all the users are listed. We could see
> the username and can search using username, first name, last name and email.
> The new requirement is to have -email verified- user enabled also appear for
> each user. This helps gateway admins to troubleshoot when users inform
> gateway access issues.
> *EDIT*: requirements changed a bit, we're showing whether the user is enabled
> instead of whether the email is verified. This is because Airavata really
> only uses the user enabled flag, so that's a truer test of whether the user
> is able to log in or not. There was also a bug where Airavata wasn't
> flagging users email verified field when enabling a user (which only happens
> when the email is verified) and that was fixed as part of this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
