We need to make sure that the Bamboo Server will be able to identify the exact agent remote address for the Agent Authentication feature.
Currently, the Sever obtains the Agent IP using HTTP "remote-address" header. If one or more proxies are between the Server and the Agent, the proxy IP will come in the remote-address header and the real Agent IP will come in the X-Forwarder-For header. If there are multiple proxies between the Server and the Agent, there will be multiple IPs defined at X-Forwarder-For.
In the way that it is implemented now, the Server will be approving the proxy IP, not the Agent IP.
[BAM-10302] Support Agent Authentication when Proxy Servers are between the Bamboo Server and the Agent
Workflow | Original: JAC Suggestion Workflow [ 3017166 ] | New: JAC Suggestion Workflow 3 [ 3602775 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2701370 ] | New: JAC Suggestion Workflow [ 3017166 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1417789 ] | New: Confluence Workflow - Public Facing v4 [ 2701370 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 606695 ] | New: Bamboo Workflow 2016 v1 [ 1417789 ] |
Remote Link | New: This issue links to "Page (Extranet)" [ 102941 ] |
Workflow | Original: Bamboo Workflow 2014 [ 594245 ] | New: Bamboo Workflow 2014 v2 [ 606695 ] |
Workflow | Original: Bamboo Workflow 2010 [ 355631 ] | New: Bamboo Workflow 2014 [ 594245 ] |
Related to https://support.atlassian.com/browse/BSP-6597