Currently, in the middle of implementing Confluence Data Center.
In regards to implementing SSL using the SSL termination methodology, the traffic looks like:
User --https--> Load Balancer --http--> node1
Has there been a use case where the data interaction has been over https even between the load balancer and Node(s):
User --https--> Load Balancer --https--> node1
The current instructions is only for running the Confluence over SSL and doesn't say much about encrypting the data interaction among the nodes and load-balancer
[Question has been updated]
"doesn't say much about encrypting the data interaction among the nodes and load-balancer" yes, the DC docs don't go into details about specific load balancers.
But a good guideline is to never leave traffic unencrypted. And have the reverse proxy running on the same server as its Jira app
Our setup is exactly this.
https -> LB -> [https (Apache ) -> http (local) Node1]
Where [ ] is all running on each server node..
So before we ever went to Data Center, or using Load Balancers our best practice was to run apache as a reserve proxy on every server running an Atlassian product (or pretty much any application container) as the front door. We then proxy to the instance running the product.
We also set the node to only response to localhost traffic for http, but allow direct https for maintenance of node.
The trick so much you have to have your load balancer and your node all have the appropriate certs and keys so they all handle the SSL.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs