Handling multiple LDAP OUs in Jira 4.3

[Mitch Lindgren]

Hi everyone,

I'm in the process of upgrading my company's Jira instance to the latest version 4.3.4. In previous versions of Jira we've been able to intergrate with LDAP just fine, by using a baseDN in the following format:

DC=subdomain,DC=mycompany,DC=com

However, as discussed in this issue, with the new authentication stack in Jira 4.3, baseDNs without organizational units cause intermittent login errors. The problem I have is that our organizational units are not organized hierarchically; they branch off into separate regional user groups at the top level. Our organization is fairly large so changing this structure is not an option.

I think I could specify multiple user directories, one for each organizational unit, but there is no way to move our existing users into the appropriate directories. Deleting and recreating all the affected accounts would take far too long, and we'd lose a lot of historical data in the process anyway (i.e. we wouldn't be able to tell which issues are/were assigned to the deletedusers).

What options, if any, do I have here?

[twong_atlassian]

Most of the time, this is due to Active Directory's ForestDNSZones entries being unresolvable DNS names. Could you simply hardcode the DNS name in your JIRA OS's /etc/hosts or equiv file?

[Jim Birch]

I don't have a Additional User DN just a Base DN (dc=xyz,dc=local) due to users in different OUs. I don't appear to have a problem on v4.4. This is in test so maybe I need some more serious testing?