Bamboo agent authentication through a reverse proxy

Gary Donovan June 5, 2013

I am using IIS as a reverse proxy in front of my bamboo installation to do URL rewriting and handl HTTPS. I want to use Agent authentication for my remote agents. However, Bamboo is unable to determine the correct IP for the connecting agent, instead thinks it is somethign like "127.0.0.1,172.17.1.1:65014" (where 172.17.1.1 is the correct IP).

Any suggestions on how to wrangle Bamboo and IIS so that this works?

1 answer

0 votes
Gary Donovan June 6, 2013

Further information:

Bamboo attempts to use the X-Forwarded-For HTTP header to determine the IP of the connecting agent. Wikipedia suggests that this header should only contain the IP address, but IIS also includes the port number (ie. it sets the header to "172.17.1.1:65014" instead of "172.17.1.1"), thus causing problems.

IIS's behaviour appears to have caused problems with other Atlassian applications also (eg. see Jira CWD-2777).

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events