airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRAVATA-2571) Have 'user enabled' appear in Admin dashboard -->Users
Date Mon, 08 Jan 2018 20:05:00 GMT

    [ https://issues.apache.org/jira/browse/AIRAVATA-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16316927#comment-16316927
] 

ASF subversion and git services commented on AIRAVATA-2571:
-----------------------------------------------------------

Commit bcdd11923c2a71bebbd722cf3b7a9c25b3ea9dc0 in airavata's branch refs/heads/AIRAVATA-2620
from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata.git;h=bcdd119 ]

Merge branch 'AIRAVATA-2571-email-verified'


> 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
>             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
(v6.4.14#64029)

Mime
View raw message