This is the documentation for Crucible 3.5. View the latest version of

Unknown macro: {spacejump}

or visit the latest Crucible documentation home page.

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

On this page:

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 a JIRA application 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 applications, Confluence, FishEye, Crucible and Bamboo can connect to a JIRA server for user management. 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.

Load on your JIRA instance

If your JIRA instance is already under high load, then using it as a User Server will increase that load.

JIRA Cloud applications not supported

You cannot use JIRA Cloud applications to manage standalone users. Cloud users and users within your self-hosted Atlassian applications need to be managed separately.

Recommendations

Your environment

Recommendation

If all the following are true:

  • Your JIRA application is not under high load.
  • You want to share user and group management across just a few applications, such as one JIRA Software server and one Confluence server, or two JIRA servers.
  • You do not need single sign-on (SSO) between your JIRA application 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 your JIRA application.

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

If one or more of the following are true:

  • If your JIRA application is already under high load.
  • 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.

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 Creating a Custom Directory Connector.

Related pages

Linking Crucible to JIRA

  • No labels

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.