Issue Details (XML | Word | Printable)

Key: CONF-11206
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Ivan Benko [Atlassian]
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Confluence

Confluence Clustered and JIRA trust delegation

Created: 25/Mar/08 01:04 AM   Updated: 07/Apr/08 09:31 PM
Component/s: Administration, Security
Affects Version/s: 2.7.2
Fix Version/s: None

Time Tracking:
Not Specified

Participants: Ivan Benko [Atlassian]
Since last comment: 35 weeks, 6 days ago
Labels:


 Description  « Hide
When setting up a trust between JIRA and a Confluence, one has to specify each individual IP address for each node apart of the cluster separated by comma; or use wildcards. As when the request is coming through the LB, one does not know which specific node will be handling that request. Hence, if the request is delivered to a confluence node that has not been added to the trusted application list in JIRA, that particular user will not be allowed to see any information coming from JIRA (for example the jiraissue macro)

To improve this I would suggest to use delegation approach. When a trust is established with one node, as each node is aware of the others, a message should be displayed suggesting the other nodes IP addresses to be inserted into JIRA admin section. Alternatively, if possible, this information could be delegated and automatically inserted into the list of trusted applications in JIRA via some remote mechanism.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.