[
https://issues.apache.org/jira/browse/AIRAVATA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385595#comment-14385595
]
pankaj saha commented on AIRAVATA-1646:
---
Hi Chris,
I haven't considered it yet, b
[
https://issues.apache.org/jira/browse/AIRAVATA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385578#comment-14385578
]
Suresh Marru commented on AIRAVATA-1646:
Hi Chris,
I fully agree we need to br
[
https://issues.apache.org/jira/browse/AIRAVATA-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14385389#comment-14385389
]
Chris A. Mattmann commented on AIRAVATA-1646:
-
This would be a good opportu
Hi Sudhakar,
Thank you for clarifying the points. So my first priority is to understand
authentication model of GridChem client and try to port it in order to
authenticate with Airavata Identity Server.
On Sat, Mar 28, 2015 at 7:12 PM, Pamidighantam, Sudhakar V <
spami...@illinois.edu> wrote:
>
In either case the file is not changed on the client side so that is not of any
significance. The migration to Airavata is in reducing the maintenance of
requirement defining code in multiple locations ( such as Airavata Server and
HPC Host etc…) into once location while managing all the relevan
