You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2014/03/17 22:23:59 UTC

[jira] (MCHANGES-327) JIRA session is not properly established using jiraUser and jiraPassword

    [ https://jira.codehaus.org/browse/MCHANGES-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343077#comment-343077 ] 

Dennis Lundberg commented on MCHANGES-327:
------------------------------------------

I think this is a duplicate. Please reopen this issue if the solution to the linked issue doesn't work for you.

> 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 was sent by Atlassian JIRA
(v6.1.6#6162)