Type: Change Request
Affects Version/s: 5.13.21, 6.0.1
Fix Version/s: 6.1.0
Datasource - Jira REST
Jira REST datasources can't be used in a DC instance when "Specific load balancing cookie" stickiness strategy is used.
We only support the the "Tomcat JSESSIONID cookie" strategy.
When I am running a DC instance of Jira
I want to tell Connect which stickiness strategy is used
So that I can use the "Jira REST API" datasources
The way Elements Connect requests Jira REST API, it needs to know which stickiness strategy is implemented to correctly build authentication request.
In the "Datasources" section of Connect admin, add a button:
- Label: "Data Center settings"
- Location: next to "Create a datasource"
- Only visible on DC instance
When this button is clicked, a dialog is displayed.
In this dialog, admin is asked to choose between two strategies:
- "Specific load balancing cookie" (default value)
- "Tomcat JSESSIONID cookie"
When the "Jira REST" datasource is used, Connect uses the appropriate cookie strategy according to the global parameter