With the release of JIRA 4.3, we introduced a slew of new search improvements and even tighter integration with Confluence for linking wiki content to your issues in JIRA. Another huge feature in this release is the new User Management capabilities of JIRA.
Simplicity for everyone
Whether you are connecting a single JIRA instance to your corporate user directory or linking JIRA and Confluence servers together, there are several benefits that everyone will enjoy.
- One login – users only have to remember a single username to login to all systems.
- One password – change your password once in any JIRA or Confluence instance and instantly update all other systems.
- One set of groups – share one set of user groups across JIRA, Confluence and your corporate directory to simplify permissions in all systems.
Centralised User Management
For administrators, user management just got a whole lot easier with JIRA 4.3. In addition to the internal JIRA directory, you can now add any number of external user directories using the new User Directory Manager – which happens to be the same as the one in Confluence 3.5.
Supported directories includes Active Directory and other LDAP directories, Atlassian Crowd, or even other JIRA instances.
Connect to Active Directory, LDAP
With the new User Directory manager, you can connect JIRA to Active Directory and other LDAP servers. All configuration details are managed directly from the JIRA admin interface – no need to mess around with XML or config files.
Connecting to Active Directory or other LDAP servers allows users to authenticate against the appropriate directory server without having JIRA store their password. User groups can also be synchronized between JIRA and your directory server.
JIRA 4.3 provides support for nested groups – assuming your directory supports them too – allowing you to add groups as members of other groups.
You can even manage group memberships and user passwords for users in your external directory directly from JIRA (granted you have read/write permissions on your external directory).
Connect to JIRA
For anyone running multiple Atlassian applications you can now connect to a single JIRA instance for authentication and user management. This is an awesome way for customers to centralise user management for their Atlassian applications.
Just like connecting to LDAP, connecting to JIRA will allow users to authenticate against JIRA while users and groups both applications can be managed in one place. At this time, only JIRA 4.3 and Confluence 3.5 can connect to a JIRA instance for user management, but we’ll be adding support for other Atlassian applications in the near future.
Note: This feature is intended for small deployments with less than 500 users and no more that 5 applications connected to JIRA. For larger deployments, you may want to consider a dedicated server, like Atlassian Crowd, to handle user management (see below).
Connect to Crowd
For growing teams we recommend using Atlassian Crowd, our SSO and identity management product.
As a dedicated server designed specifically for handling user management, Atlassian Crowd is perfect for teams requiring high availability and scale.
Crowd also provides single sign-on in order for users to login once and automatically be able to access all other protected applications.
Common deployment scenarios
With all these new user management features, there are several different ways to deploy JIRA in your environment.
That’s we put together a short video summarizing common deployment scenarios for JIRA and your Atlassian developer tools.