Skip to main content

Prepare Nexus Repository 2 and Atlassian Crowd

Nexus Repository 2

Prepare NXRM for Atlassian Crowd

Atlassian Crowd support is preinstalled and ready to configure in Nexus Repository Manager Pro 2.7+. In older versions, Crowd support is implemented as an optional plugin that comes as part of any Nexus Repository Manager Pro download. The directory containing the plugin code is called either enterprise-crowd-plugin-X.Y.Z or nexus-crowd-plugin-X.Y.Z. Install the plugin following the instructions in Managing Plugins.


Using LDAP and Crowd Realms together in the repository manager may work, but this is not supported. If you already use LDAP support, we recommend adding your LDAP server as a Crowd directory accessible to the Crowd nexus application instead of using both LDAP and Crowd realms in the repository manager.

Prepare Atlassian Crowd


Always use the latest version of Crowd available at the time your version of Nexus Repository Manager Pro was released. When upgrading to a newer Crowd server, carefully review the Crowd server release notes for REST API backwards compatibility issues.

Crowd support in Nexus Repository Manager Pro 2.7 and greater only works in Crowd versions (2.1+) that support the Crowd REST API. Older versions use a deprecated SOAP-based API and are less reliable and performant.

Crowd support is actively tested with the highest available version of Crowd at the time Nexus Repository Manager Pro is released.

Configure a Nexus Repository Manager Pro Application in the Atlassian Crowd Server


These instructions are a general guide to adding an application to Crowd. For current detailed instructions, visit the official Crowd documentation.

To connect Nexus Repository Manager Pro to Atlassian’s Crowd, you will need to configure Nexus Repository Manager Pro as an application in Crowd.

  1. Login to Crowd as a user with administrative rights

  2. Click on the Applications tab

  3. Click Add Application to display the form, shown in Figure 9.1, “Creating a Nexus Crowd Application”, and create a new application with the following values in the Details tab of the Add Application form as the following example:

    • Application Type: Generic Application

    • Name: nexus

    • Description: Sonatype Nexus Professional

  4. Choose a password for this application. Nexus Repository Manager will use this password to authenticate with the Crowd server. Click on the Next button.


Figure 9.1. Creating a Nexus Crowd Application

Clicking on Next will advance the form to the Connection tab shown in Figure 9.2, “Creating a Nexus Crowd Application Connection”. In this tab you need to supply the URL of your application instance and the remote IP address for Nexus Repository Manager Pro. Figure 9.2, “Creating a Nexus Crowd Application Connection”, shows the Connection form configured for a local instance of Nexus Repository Manager Pro. If you were configuring Crowd and Nexus Repository Manager Pro in a production environment, you would supply the URL that users would use to load the repository manager user interface in a web browser and you would supply the IP address that the repository manager will be connecting from. Once you have completed the Connection form, click on Next to advance to the Directories form shown in Figure 9.3, “Choosing Atlassian Crowd Application Directories”.


Figure 9.2. Creating a Nexus Crowd Application Connection

The Directories form allows you to select the user directory used for Nexus Repository Manager authentication. In this example, the default User Management directory will be used.


Figure 9.3. Choosing Atlassian Crowd Application Directories

Clicking on the Next button in the Directories form advances to the Authorisation form shown in Figure 9.4, “Creating a Nexus Crowd Application Authorization”. If any of the directories selected in the previous form contain groups, each group is displayed on this form next to a checkbox. You can select Allow all users to authenticate for a directory or you can select specific groups that are allowed to authenticate to Nexus Repository Manager Pro via Crowd. This option would be used if you wanted to limit repository manager access to specific subgroups within a larger Crowd directory. If your entire organization is stored in a single Crowd directory, you may want to limit repository manager access to a group that contains only developers and administrators.


Figure 9.4. Creating a Nexus Crowd Application Authorization