[
https://issues.apache.org/jira/browse/AIRAVATA-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma closed AIRAVATA-1617.
---------------------------
Resolution: Fixed
With Airavata 0.16 we provide login user name to resources in gateway
preferences in admin dashboard for SSH communications. PGA interfaces
facilitates this.
GFAC users the given username to login to the resource.
Tested with current PGAs. dev.seagrid.org, testdrive.org, etc...
> Enhance Gateway Profile to add resource specific user names
> -----------------------------------------------------------
>
> Key: AIRAVATA-1617
> URL: https://issues.apache.org/jira/browse/AIRAVATA-1617
> Project: Airavata
> Issue Type: Improvement
> Reporter: Suresh Marru
> Assignee: Suresh Marru
>
> Currently Airavata suppresses the notion of unix user names on various
> compute resources. This assumption works well for GSI based single sign on
> approach. For SSH based authentication, explicit list of user names is
> required. Steps to add this feature to Airavata:
> * Add loginUserName field to compute resource preference within the gateway
> profile.
> * Update App Catalog UI and all the existing resource descriptions.
> * Change GFac to use this new field instead of the user name from the
> credential store.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
