Improve HTTP authentication for Jira client

Description

Backbone is connecting via HTTP(s) to Jira. At the moment Backbone sends HTTP authentication information in every request it's performing. However, this leads in some scenarios to lots of sessions and may affect the performance of the overall Jira system.
Especially systems with lots of synchronized issues and synchronizations are facing this problem.

Suggested Improvement
Backbone's mechanism to reuse an HTTP session should be improved so that it works for all Jiras. In addition, by using a session based authentication, the number of necessary authentications can be improved as well.

Environment

None

Status

Assignee

Unassigned

Reporter

Sync User [K15t]

Labels

None

Participants

None

Deployment

Server

Components

Fix versions

Affects versions

Priority

Major
Configure