Actually it is supported, just enter more than one LDAP URL separating them by spaces, e.g. "ldap://ldap1:389 ldap://ldap2:389 ldap://ldap3:389". This is a documented method of creating InitialContext, see section URL for Configuring Service Providers of http://docs.oracle.com/javase/jndi/tutorial/ldap/misc/url.html page if interested.
I think there was never formal feature request raised for this so this was not added deliberately. Instead this is side effect of using standard JRE ldap client, apparently valuable one. I have tested that quickly yesterday and seems to be working fine. In order to provide proper load balancing (with health checks and actual load monitoring) one may prefer to look for proper load balancing solution, though.
Actually it is supported [by FishEye]
Just to clarify, this is provided by the JNDI LDAP Service Provide from JRE and we have no reasons to think this is not ready for production use. At the same time we have not tested than extensively enough to confirm we support this feature, although we would endeavour to address any issues related to such configuration.
Hope that make sense,
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