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?
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).
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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