[jira] [Commented] (AIRAVATA-2463) Throws system exception when tried to submit gateway request with already existing gateway name

[ https://issues.apache.org/jira/browse/AIRAVATA-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071829#comment-16071829 ] Marcus Christie commented on AIRAVATA-2463: --- A meaningful error message is now displayed

[jira] [Commented] (AIRAVATA-2468) When requesting for a gateway validate the email address format.

[ https://issues.apache.org/jira/browse/AIRAVATA-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071828#comment-16071828 ] Marcus Christie commented on AIRAVATA-2468: --- Looks like email validation is working. When I

[jira] [Commented] (AIRAVATA-2469) New gateway providers cannot create a gateway request.

[ https://issues.apache.org/jira/browse/AIRAVATA-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071826#comment-16071826 ] Marcus Christie commented on AIRAVATA-2469: --- [~tilaks26], that is right. I think adding

[jira] [Commented] (AIRAVATA-2233) Window should close upon admin clicking a button in 'Approve Gateway Request'

[ https://issues.apache.org/jira/browse/AIRAVATA-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071717#comment-16071717 ] Eroma commented on AIRAVATA-2233: - This is required because currently when statuses are updated it is

[jira] [Closed] (AIRAVATA-2440) With keycloak, my username is changed, results a new data directory creation

[ https://issues.apache.org/jira/browse/AIRAVATA-2440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2440. --- tested and verified in https://dev.seagrid.org/ Didnt experience the issue after the fix. > With keycloak,

[jira] [Closed] (AIRAVATA-2457) In SciGaP portal notices are not visible to gateway providers.

[ https://issues.apache.org/jira/browse/AIRAVATA-2457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma closed AIRAVATA-2457. --- Tested and verified in https://dev.scigap.org/ for both new keycloak and migrated gateway provider users. >

[jira] [Comment Edited] (AIRAVATA-2470) When existing gateway provider tries to update the second part of the gateway reqest

[ https://issues.apache.org/jira/browse/AIRAVATA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071706#comment-16071706 ] Eroma edited comment on AIRAVATA-2470 at 7/2/17 4:23 PM: - Same error exception

[jira] [Commented] (AIRAVATA-2470) When existing gateway provider tries to update the second part of the gateway reqest

[ https://issues.apache.org/jira/browse/AIRAVATA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071706#comment-16071706 ] Eroma commented on AIRAVATA-2470: - Same error exception when gateway provider tries to cancel the

[jira] [Commented] (AIRAVATA-2469) New gateway providers cannot create a gateway request.

[ https://issues.apache.org/jira/browse/AIRAVATA-2469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071696#comment-16071696 ] Sneha Tilak commented on AIRAVATA-2469: --- This is an error with filters.php. Earlier, the role

[jira] [Issue Comment Deleted] (AIRAVATA-2369) Gateway provider (who requests for a gateway) clicks User settings in SciGaP portal cannot navigate back to gateway requesting UI

[ https://issues.apache.org/jira/browse/AIRAVATA-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2369: Comment: was deleted (was: Gateway requests can be created successfully using the same user in

[jira] [Commented] (AIRAVATA-2369) Gateway provider (who requests for a gateway) clicks User settings in SciGaP portal cannot navigate back to gateway requesting UI

[ https://issues.apache.org/jira/browse/AIRAVATA-2369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16071671#comment-16071671 ] Eroma commented on AIRAVATA-2369: - When clicked on the logo and then click on the dashboard to navigate

[jira] [Updated] (AIRAVATA-2463) Throws system exception when tried to submit gateway request with already existing gateway name

[ https://issues.apache.org/jira/browse/AIRAVATA-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2463: Summary: Throws system exception when tried to submit gateway request with already existing gateway name

[jira] [Created] (AIRAVATA-2470) When existing gateway provider tries to update the second part of the gateway reqest

Eroma created AIRAVATA-2470: --- Summary: When existing gateway provider tries to update the second part of the gateway reqest Key: AIRAVATA-2470 URL: https://issues.apache.org/jira/browse/AIRAVATA-2470

[jira] [Updated] (AIRAVATA-2468) When requesting for a gateway validate the email address format.

[ https://issues.apache.org/jira/browse/AIRAVATA-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2468: Description: When requesting for a gateway, gave 'test' as the email and when saved. (was: When

[jira] [Updated] (AIRAVATA-2470) When existing gateway provider tries to update the second part of the gateway reqest

[ https://issues.apache.org/jira/browse/AIRAVATA-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eroma updated AIRAVATA-2470: Attachment: Screen Shot 2017-07-02 at 10.40.54 AM.png > When existing gateway provider tries to update

[jira] [Created] (AIRAVATA-2469) New gateway providers cannot create a gateway request.

Eroma created AIRAVATA-2469: --- Summary: New gateway providers cannot create a gateway request. Key: AIRAVATA-2469 URL: https://issues.apache.org/jira/browse/AIRAVATA-2469 Project: Airavata Issue

[jira] [Created] (AIRAVATA-2468) When requesting for a gateway validate the email address format.

Eroma created AIRAVATA-2468: --- Summary: When requesting for a gateway validate the email address format. Key: AIRAVATA-2468 URL: https://issues.apache.org/jira/browse/AIRAVATA-2468 Project: Airavata