[Other doc versions]
This page does not apply to JIRA Cloud; you can't use JIRA Cloud to manage your Stash users.
You can connect Stash to an existing Atlassian JIRA instance to delegate Stash user and group management, and authentication. Stash provides a "read-only" connection to JIRA for user management. This means that users and groups, fetched from JIRA, can only be modified or updated in that JIRA server, rather than in Stash.
Choose this option, as an alternative to Atlassian Crowd, for simple configurations with a limited number of users. Note that Stash can only connect to a JIRA server running JIRA 4.3 or later.
Connecting Stash and JIRA is a 3-step process:
Also on this page:
You need to be an administrator in JIRA and a system administrator in Stash to perform the following tasks.
In order to use Stash, users must be a member of the
Stash-users group or have Stash global permissions. Follow these steps to configure your Stash groups in JIRA:
stash-administratorsgroups in JIRA.
Connecting Atlassian Stash to JIRA for user management is not sufficient, by itself, to allow your users to log in to Stash. You must also grant them access to Stash 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 Stash license allows. If the license limit is exceeded, your developers will not be able to push commits to repositories, and Stash will display a warning banner. See this FAQ.
See also this information about deleting users and groups in Stash.
A meaningful name that will help you to identify this Jira server in the list of directory servers. Examples:
The web address of your Jira server. Examples:
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.
The password used by your application when accessing the Jira server that acts as user manager.
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.
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.