airavata-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (AIRAVATA-2385) SciGaP portal need to check for duplicating gateway names and URLs at the time of user creating/submitting the gateway request.
Date Fri, 30 Jun 2017 17:51:00 GMT


ASF GitHub Bot commented on AIRAVATA-2385:

GitHub user tilaks26 opened a pull request:

    PGA Enhancements and Bug Fixes

    This PR is created for all the changes made to the PGA portal. The following issues were
fixed -
    [AIRAVATA-2385] - Portal checks for Gateway requests with the same name or URL as that
of an already approved/created/deployed Gateway.
    [AIRAVATA-2463] - The portal now accepts duplicate Gateway requests.
    [AIRAVATA-2199] - The modified flow includes the following states: REQUESTED (when a new
Gateway is requested), APPROVED (when a Gateway is approved by the Admin), DENIED (when a
Gateway is denied by the Admin), CREATED (when the Gateway details have been filled and the
Admin chooses to create a Tenant), DEPLOYED (when the SciGaP Admin deploys a Gateway after
which the provider can use it), DEACTIVATED (when the Gateway is no longer in use).
    [AIRAVATA-2325] - The auth keys are generated only when the Admin chooses to create the
    [AIRAVATA-2199] - The Gateway status changes to APPROVED when the Admin approves the request
and CREATED when the Admin created the tenant.
    [AIRAVATA-2079] - An email is sent to the Admin every time a user requests for a new Gateway.
Also, an email is sent to the Gateway Provider and Admin when ever there is a change or update
in the Gateway details.
    [AIRAVATA-2046] - The Admin can edit the gateway request until the tenant is created.
    [AIRAVATA-2022] - When a new Gateway is requested, the message displayed is "Your request
for Gateway <Gateway Name> has been created."
    [AIRAVATA-2404] - When the Admin creates a tenant, the IAMAdminServices's setUpGateway()
method is invoked which then generated the Keycloak secret keys.
    [AIRAVATA-2446] - The request for a new Gateway now asks for minimal information which
includes the Gateway Name, Contact Email ID and Public Project Description. Once approved
by the Admin, the provider can update the other details through a form.
    [AIRAVATA-1989] - The 'Add a new Gateway' button on the Admin's portal now redirects to
a standalone new form where the Admin can create a new Gateway which directly goes into the
    Since there were many changes to be made with respect to the PGA, I have created just
one PR with all the changes.

You can merge this pull request into a Git repository by running:

    $ git pull develop

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #58
commit f33f4226893cc986df260b7097fc254f69c8c511
Author: Sneha Tilak <>
Date:   2017-06-29T21:12:12Z

    Adding PGA enhancements and bug fixes

commit 516b13aeb3b765c1dd93b726de06da0c7d4659a5
Author: Sneha Tilak <>
Date:   2017-06-29T21:26:28Z

    Modifying email function

commit fba2720f89413ff9e7ff113eee9d275a9e71c58c
Author: Sneha Tilak <>
Date:   2017-06-30T16:02:30Z

    Merge remote-tracking branch 'upstream/develop' into develop

commit 75d43f746797e142a6750e577c8dfb8a4d64525c
Author: Sneha Tilak <>
Date:   2017-06-30T17:26:41Z

    Modified view to return duplicate gateway requests


> SciGaP portal need to check for duplicating gateway names and URLs at the time of user
creating/submitting the gateway request.
> -------------------------------------------------------------------------------------------------------------------------------
>                 Key: AIRAVATA-2385
>                 URL:
>             Project: Airavata
>          Issue Type: Improvement
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.17
>            Reporter: Eroma
>            Assignee: Sneha Tilak
>             Fix For: 0.18
> Currently wt the time of creating or submitting the request this is not checked. 

This message was sent by Atlassian JIRA

View raw message