[
https://jira.codehaus.org/browse/MCHANGES-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Rivera updated MCHANGES-327:
----------------------------------
Summary: JIRA session is not properly established using jiraUser and
jiraPassword (was: JIRA session is not properly established using jiraUsername
and jiraPassword)
> JIRA session is not properly established using jiraUser and jiraPassword
> ------------------------------------------------------------------------
>
> Key: MCHANGES-327
> URL: https://jira.codehaus.org/browse/MCHANGES-327
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
> Affects Versions: 2.9
> Reporter: Diego Rivera
>
> When using jiraUser and jiraPassword for authentication (in lieu of webUser
> and webPassword), the session cookie is not preserved in order to maintain
> the session authentication information for subsequent REST requests.
> This means that although authentication succeeds, subsequent REST requests
> don't benefit from the long-running session that was established.
> The JSESSIONID cookie value needs to be captured from the original auth
> request and preserved throughout all other REST invocations.
> Using webUser and webPassword works, though, so at least that workaround is
> there.
--
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
