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, 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.
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:
| Your environment meets the optimal requirements for using JIRA for user management. |
If one or more of the following are true:
| 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:
|