On this page

Related content

Still need help?

This page does not apply to Jira Software Cloud; you can't use Jira Software Cloud to manage your Bitbucket Server users.

You can connect Bitbucket Server to an existing Atlassian Jira Software instance to delegate Bitbucket Server user and group management, and authentication. Bitbucket Server provides a "read-only" connection to Jira Software for user management. This means that users and groups, fetched from Jira Software, can only be modified or updated in that Jira Software server, rather than in Bitbucket Server.

Choose this option, as an alternative to Atlassian Crowd, for simple configurations with a limited number of users. Note that Bitbucket Server can only connect to an instance running Jira Software 4.3 or later.

Define the directory order, on the 'User Directories' screen, by clicking the arrows for each directory. The directory order has the following effects:

The order of the directories is the order in which they will be searched for users and groups.

Changes to users and groups will be made only in the first directory where the application has permission to make changes.

3. Set up Bitbucket Server users and groups in Jira Software

In order to use Bitbucket Server, users must be a member of the Bitbucket Server-users group or have Bitbucket Server global permissions. Follow these steps to configure your Bitbucket Server groups in Jira Software:

Add the bitbucket-users and bitbucket-administrators groups in Jira Software.

Add your own username as a member of both of the above groups.

Choose one of the following methods to give your existing Jira Software users access to Bitbucket Server:

Option 1: In Jira Software, find the groups that the relevant users belong to. Add those groups as members of one or both of the above Bitbucket Server groups.

Connecting Atlassian Bitbucket Server to Jira Software for user management is not sufficient, by itself, to allow your users to log in to Bitbucket Server. You must also grant them access to Bitbucket Server by using one of the above 2 options.

We recommend that you use groups instead of individual accounts when granting permissions. However, be careful not to add more users to those groups that your Bitbucket Server license allows. If the license limit is exceeded, your developers will not be able to push commits to repositories, and Bitbucket Server will display a warning banner. Seethis FAQ.

Server settings

A meaningful name that will help you to identify this Jira server in the list of directory servers. Examples:

Jira Service Desk Server

My Company Jira

Server URL

The web address of your Jira server. Examples:

http://www.example.com:8080

http://jira.example.com

Application Name

The name used by your application when accessing the Jira server that acts as user manager. Note that you will also need to define your application to that Jira server, via the 'Other Applications' option in the 'Users, Groups & Roles' section of the 'Administration' menu.

Application Password

The password used by your application when accessing the Jira server that acts as user manager.

Jira Software server permissions

Setting

Description

Read Only

The users, groups and memberships in this directory are retrieved from the Jira server that is acting as user manager. They can only be modified via that JIRA server.

Advanced settings

Setting

Description

Enable Nested Groups

Enable or disable support for nested groups. Before enabling nested groups, please check to see if nested groups are enabled on the JIRA server that is acting as user manager. When nested groups are enabled, you can define a group as a member of another group. If you are using groups to manage permissions, you can create nested groups to allow inheritance of permissions from one group to its sub-groups.

Enable Incremental Synchronization

Enable or disable incremental synchronization. Only changes since the last synchronization will be retrieved when synchronizing a directory.

Synchronization Interval (minutes)

Synchronization is the process by which the application updates its internal store of user data to agree with the data on the directory server. The application will send a request to your directory server every x minutes, where 'x' is the number specified here. The default value is 60 minutes.