Crucible 2.7 : User Management Limitations and Recommendations

This page describes the optimal configurations and limitations that apply when you are connecting Crucible to JIRA for user management.

Recommendations for Connecting to JIRA for User Management

Please consider the following limitations and recommendations when connecting to a JIRA server for user management.

Single Sign-On Across Multiple Applications is Not Supported

When you connect to JIRA for user management, you will not have single sign-on across the applications connected in this way. JIRA, when acting as a directory manager, does not support SSO.

Custom Application Connectors are Not Supported

JIRA, Confluence, FishEye and Crucible can connect to a JIRA server for user management. We intend to add support for Bamboo at some time in the future. Custom application connectors will need to use the new REST API.

Custom Directories are Not Supported

Earlier versions of JIRA supported OSUser Providers. It was therefore possible write a special provider to obtain user information from any external user directory. This is no longer the case.

Optimal Number of Users and Applications

Please consider the following limitations when connecting to a JIRA server for user management:

  • Maximum 500 users.
  • Maximum 5 connected applications.

Recommendations

Your environment

Recommendation

If all the following are true:

  • You have fewer than 500 users.
  • You want to share user and group management across just a few applications, such as one JIRA server and one Confluence server, or two JIRA servers.
  • You do not need single sign-on (SSO) between JIRA and Confluence, or between two JIRA servers.
  • You do not have custom application connectors. Or, if you do have them, you are happy to convert them to use the new REST API.
  • You are happy to shut down all your servers when you need to upgrade JIRA.
  • You do not have Bamboo. Or, if you do have Bamboo, you are happy not to integrate its user management with JIRA at the moment. You are happy to wait until at least July 2011, perhaps longer.

Your environment meets the optimal requirements for using JIRA for user management.

If one or more of the following are true:

  • You have more than 500 users.
  • You want to share user and group management across more than 5 applications.
  • You need single sign-on (SSO) across multiple applications.
  • You have custom applications integrated via the Crowd SOAP API, and you cannot convert them to use the new REST API.
  • You are not happy to shut down all your servers when you need to upgrade JIRA.
  • You have Bamboo and you want to integrate its user management with JIRA immediately.

We recommend that you install Atlassian Crowd for user management and SSO.

If you are considering creating a custom directory connector to define your own storage for users and groups

Please see if one of the following solutions will work for you:

  • If you have written a custom provider to support a specific LDAP schema, please check the supported LDAP schemas to see if you can use one of them instead.
  • If you have written a custom provider to support nested groups, please consider enabling nested groups in the supported directory connectors instead.
  • If you have written a custom provider to connect to your own database, please consider loading the data into the application's database instead.
  • If you need to keep the custom directory connection, please consider whether Atlassian Crowd meets your requirements. See the documentation on developing a custom directory connector for Crowd.
Related Topics

JIRA Integration in Crucible