You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Saminda Wijeratne (JIRA)" <ji...@apache.org> on 2013/08/15 18:26:49 UTC

[jira] [Resolved] (AIRAVATA-899) API need enhancement so user can set a user identifier into Context header

     [ https://issues.apache.org/jira/browse/AIRAVATA-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Saminda Wijeratne resolved AIRAVATA-899.
----------------------------------------

    Resolution: Fixed

The user identifier that was passed to the context header builder had dual purpose (as the user who is submitting the workflow execution & user information regarding the execution of the workflow). However this jira is depicting one of those usecases is interfearing with the other because of sharing the same user value where the user needs to be two different values. Thus I've updated the code base to to have a different submission user field in the context header.
Committed revision 1514348.
                
> API need enhancement so user can set a user identifier into Context header
> --------------------------------------------------------------------------
>
>                 Key: AIRAVATA-899
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-899
>             Project: Airavata
>          Issue Type: Improvement
>          Components: Airavata Client
>    Affects Versions: 0.8
>            Reporter: Raminderjeet Singh
>
> Currently Airavata user and Job submission user is defaulted to airavata user in the context header even user try to set ExperimentAdvanceOptions.setExperimentExecutionUser(user) in Airavata API. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira