[Other doc versions]
[Doc downloads (PDF, HTML, XML)]
You can configure Stash to use Atlassian Crowd for user and group management, and for authentication and authorisation.
Atlassian Crowd is an application security framework that handles authentication and authorisation for your web-based applications. With Crowd you can integrate multiple web applications and user directories, with support for single sign-on (SSO) and centralised identity management. See the Crowd Administration Guide.
Connect to Crowd if you want to use Crowd to manage existing users and groups in multiple directory types, or if you have users of other web-based applications.
See also this information about deleting users and groups in Stash.
Connecting Atlassian Stash to your external directory is not sufficient to allow your users to log in to Stash. You must explicitly grant them access to Stash in the global permission screen.
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.
To connect Stash to Crowd:
A meaningful name that will help you to identify this Crowd server amongst your list of directory servers. Examples:
The web address of your Crowd console server. Examples:
The name of your application, as recognized by your Crowd server. Note that you will need to define the application in Crowd too, using the Crowd administration Console. See the Crowd documentation on adding an application.
The password which the application will use when it authenticates against the Crowd framework as a client. This must be the same as the password you have registered in Crowd for this application. See the Crowd documentation on adding an application.
Stash offers Read Only permissions for Crowd directories. The users, groups and memberships in Crowd directories are retrieved from Crowd and can only be modified from Crowd. You cannot modify Crowd users, groups or memberships using the Stash administration screens.
For local Stash directories, Read Only and Read/Write permissions are available.
Enable Nested Groups
Enable or disable support for nested groups. Before enabling nested groups, please check to see if the user directory or directories in Crowd support nested groups. 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. Note that full synchronization is always executed when restarting the application.|
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.
Once the Crowd directory has been set up, you can enable Crowd SSO integration by adding the following setting to
shared/stash-config.properties in the Stash home directory (create this file if it doesn't exist yet):
Please note that you will need to correctly set up the domains of the applications involved in SSO. See Crowd SSO Domain examples.
In addition to this property, Crowd SSO integration can be tuned using the system properties described on Stash config properties.
When Stash is connected to Crowd you can map Stash to multiple user directories in Crowd.
For Crowd 2.8, and later versions, there are two different membership schemes that Crowd can use when multiple directories are mapped to an integrated application, and duplicate user names and group names are used across those directories. The schemes are called 'aggregating membership' and 'non-aggregating membership' and are used to determine the effective group memberships that Stash uses for authorisation. See Effective memberships with multiple directories for more information about these two schemes in Crowd.
An administrator can set the aggregation scheme that Stash uses when integrated with Crowd. Go to the Directories tab for the Stash instance in Crowd, and check Aggregate group memberships across directories to use the 'aggregating membership' scheme. When the checkbox is clear 'non-aggregating membership' is used.
Note that changing the aggregation scheme can affect the authorisation permissions for your Stash users, and how directory update operations are performed.