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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.9
• Component/s: jira
• Assignee: Unassigned
• Reporter: Diego Rivera
• Created: 22/Jan/14 09:51
• Updated: 17/Mar/14 16:23
• Resolved: 17/Mar/14 16:23

Description

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.

Issue Links

• duplicates: MCHANGES-324 Plugin logs into JIRA, but doesn't seem to make the status request with the session