Bamboo agent authentication through a reverse proxy

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

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,561 views 0 6
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you