User management limitations and recommendations
This page describes the optimal configurations and limitations that apply when you are connecting Fisheye to Jira for user management.
On this page:
Recommendations for connecting to Jira 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.
If all the following are true:
Your environment meets the optimal requirements for using a JIRA application 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: