[
https://issues.apache.org/jira/browse/AIRAVATA-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313736#comment-16313736
]
Eroma edited comment on AIRAVATA-2509 at 1/9/18 8:20 PM:
---------------------------------------------------------
Tested in https://dev.seagrid.org and https://dev.scigap.org/ using gmail and
IU institute emails addresses.
Test cases
https://dev.seagrid.org
1. Create a new gateway account in dev.seagrid using gmail account. - PASS
2. Create a new gateway account in dev.seagrid using gmail account and leave
'Email (again)' space and NULL. - PASS
3. Create a new gateway account in dev.seagrid using institute (IU) account. -
PASS
4. Create a new gateway account in dev.seagrid using gmail account and give a
different gmail account for 'Email (again)'- (Error message thrown saying that
two doesn't match) - PASS
5. Create a new gateway account in dev.seagrid using institute account and give
a different institute account for 'Email (again)' (if possible both having same
text prior to @) - PASS
*+6. Test email format validations in dev.seagrid - (Can improve. @ sign and
string following that are checked at field level but .com is only validated
after user clicks Create. Tested without @ sign, without string following @
sign and 2 @ signs and with and without .com Also tested special characters
like !@#$% and -) - PASS+*
7. Test user not providing surname at account creation. Field is mandatory.
User has to enter – PASS
8. Test the first name and surname provided by user appearing in the email sent
with gmail– PASS
9. Test the first name and surname provided by user appearing in the email sent
with institute email– (This seem to have no impact on institute email. It seems
to use the first name and last name existing at the institute linked to the
email. This can be ignored for institute emails.) – N/A
10. Test password reset for user with institute email – PASS
11. Test password reset for user with gmail email - PASS
12. Test verification link validation failure and system sending it for the
second time with gmail - PASS
13. Test verification link validation failure and system sending it for the
second time with institute – PASS
14. Test CILogon account creation. - PASS
https://dev.scigap.org/
*+1. Create a new gateway account in dev.scigap using gmail account. – FAIL for
some usernames. (https://issues.apache.org/jira/browse/AIRAVATA-2626)+*
2. Create a new gateway account in dev.seagrid using gmail account and leave
'Email (again)' space and NULL. - PASS
3. Create a new gateway account in dev.scigap using institute (IU) account. -
PASS
4. Create a new gateway account in dev.scigap using gmail account and give a
different gmail account for 'Email (again)' - PASS
5. Create a new gateway account in dev.scigap using institute account and give
a different institute account for 'Email (again)' if possible both having same
text prior to @) - PASS
*+6. Test email format validations in dev.seagrid - PASS (Can improve. @ sign
and string following that are checked at field level but .com is only validated
after user clicks Create. Tested without @ sign, without string following @
sign and 2 @ signs and with and without .com. Also tested special characters
like !@#$% and -) - PASS+*
7. Test user not providing surname at account creation. Field is mandatory.
User has to enter – PASS
8. Test the first name and surname provided by user appearing in the email sent
with gmail – PASS
9. Test the first name and surname provided by user appearing in the email sent
with institute email (For Indiana.edu the provided first and last name appears.
But for iu.edu it’s the names with the institute.)– PASS
10. Test password reset for user with institute email. - PASS
11. Test password reset for user with gmail email. - PASS
12. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using gmail account. Provide the
same gmail account as gateway contact email. – PASS
13. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using institute account. Provide the
same institute account as gateway contact email. – PASS
14. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using gmail account. Provide a
different email account, not the one given for account creation. - PASS
15. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using institute account. Provide a
different email account, not the one given for account creation. - PASS
16. Test verification link validation failure and system sending it for the
second time with gmail. - PASS
*+17. Test verification link validation failure and system sending it for the
second time with institute – (Minor issue reported
https://issues.apache.org/jira/browse/AIRAVATA-2628)PASS+*
18. Test CILogon account creation. – CILogon not enabled in the portal.
was (Author: eroma_a):
Tested in https://dev.seagrid.org and https://dev.scigap.org/ using gmail and
IU institute emails addresses.
Test cases
https://dev.seagrid.org
1. Create a new gateway account in dev.seagrid using gmail account. - PASS
2. Create a new gateway account in dev.seagrid using gmail account and leave
'Email (again)' space and NULL. - PASS
3. Create a new gateway account in dev.seagrid using institute (IU) account. -
PASS
4. Create a new gateway account in dev.seagrid using gmail account and give a
different gmail account for 'Email (again)'- (Error message thrown saying that
two doesn't match) - PASS
5. Create a new gateway account in dev.seagrid using institute account and give
a different institute account for 'Email (again)' (if possible both having same
text prior to @) - PASS
*+6. Test email format validations in dev.seagrid - (Can improve. @ sign and
string following that are checked at field level but .com is only validated
after user clicks Create. Tested without @ sign, without string following @
sign and 2 @ signs and with and without .com Also tested special characters
like !@#$% and -) - PASS+*
7. Test user not providing surname at account creation. Field is mandatory.
User has to enter – PASS
8. Test the first name and surname provided by user appearing in the email sent
with gmail– PASS
9. Test the first name and surname provided by user appearing in the email sent
with institute email– (This seem to have no impact on institute email. It seems
to use the first name and last name existing at the institute linked to the
email. This can be ignored for institute emails.) – N/A
10. Test password reset for user with institute email – PASS
11. Test password reset for user with gmail email - PASS
12. Test verification link validation failure and system sending it for the
second time with gmail - PASS
13. Test verification link validation failure and system sending it for the
second time with institute – PASS
14. Test CILogon account creation. - PASS
https://dev.scigap.org/
*+1. Create a new gateway account in dev.scigap using gmail account. – FAIL for
some usernames. (https://issues.apache.org/jira/browse/AIRAVATA-2626)+*
2. Create a new gateway account in dev.seagrid using gmail account and leave
'Email (again)' space and NULL. - PASS
3. Create a new gateway account in dev.scigap using institute (IU) account. -
PASS
4. Create a new gateway account in dev.scigap using gmail account and give a
different gmail account for 'Email (again)' - PASS
5. Create a new gateway account in dev.scigap using institute account and give
a different institute account for 'Email (again)' if possible both having same
text prior to @) - PASS
*+6. Test email format validations in dev.seagrid - PASS (Can improve. @ sign
and string following that are checked at field level but .com is only validated
after user clicks Create. Tested without @ sign, without string following @
sign and 2 @ signs and with and without .com. Also tested special characters
like !@#$% and -) - PASS+*
7. Test user not providing surname at account creation. Field is mandatory.
User has to enter – PASS
8. Test the first name and surname provided by user appearing in the email sent
with gmail – PASS
9. Test the first name and surname provided by user appearing in the email sent
with institute email (For Indiana.edu the provided first and last name appears.
But for iu.edu it’s the names with the institute.)– PASS
10. Test password reset for user with institute email. - PASS
11. Test password reset for user with gmail email. - PASS
12. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using gmail account. Provide the
same gmail account as gateway contact email. – PASS
13. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using institute account. Provide the
same institute account as gateway contact email. – PASS
14. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using gmail account. Provide a
different email account, not the one given for account creation. - PASS
15. Create a gateway request, update it after approval and test receiving
notifications after gateway tenant created using institute account. Provide a
different email account, not the one given for account creation. - PASS
16. Test verification link validation failure and system sending it for the
second time with gmail. - PASS
*+17. Test verification link validation failure and system sending it for the
second time with institute – (Minor issue reported
https://issues.apache.org/jira/browse/AIRAVATA-2628)PASS+*
18. Test CILogon account creation. – CILogon not enabled in the portal.
> Account confirmation, password reset emails not making it to user
> -----------------------------------------------------------------
>
> Key: AIRAVATA-2509
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2509
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Reporter: Marcus Christie
> Assignee: Neeraj Lad
> Priority: Critical
> Labels: newbie
>
> Email confirmation emails (when creating an account) and password reset
> emails aren't always making it to users. There are at least a couple reasons
> for this:
> * the emails are getting flagged as spam and the user doesn't check the spam
> folder
> ** perhaps in some cases the emails never ever reach the user if they are
> marked as spam and stopped at the email server
> * the user mis-types their email address
> Possible fixes:
> * Can we find out what is causing emails to be flagged as spam? Is there a
> way to make the emails seem less "spammy"?
> ** See for example https://stackoverflow.com/a/396
> * Require that users type in their email address twice in order to confirm
> it. This should help prevent typos.
> * Can we determine if an email bounces back? This might be tricky since I
> think email bounce backs are asynchronous. Perhaps having the user confirm
> their email address is the best we can do.
> Workarounds:
> * use CILogon instead of account creation/password reset.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
