Repository Management with Nexus - 2.12

Share

9.2. Prepare Atlassian Crowd

9.2.1. Compatibility

Always use the latest version of Crowd available at the time your version of Nexus Repository Manager 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 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 is released.

9.2.2. Configure a Nexus Repository Manager Application in the Atlassian Crowd Server

[Note]

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 to Atlassian’s Crowd, you will need to configure Nexus Repository Manager 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:

    • Application Type: Generic Application
    • Name: nexus
    • Description: Nexus Repository Manager
  4. Choose a password for this application. Nexus will use this password to authenticate with the Crowd server. Click on the Next button.
figs/web/crowd_new-app.png

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. Figure 9.2, “Creating a Nexus Crowd Application Connection”, shows the Connection form configured for a local instance of Nexus Repository Manager. If you were configuring Crowd and Nexus Repository Manager 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”.

figs/web/crowd_new-app-connection.png

Figure 9.2. Creating a Nexus Crowd Application Connection


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

figs/web/crowd_new-app-directories.png

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 for a directory or you can select specific groups that are allowed to authenticate to Nexus Repository Manager 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.

figs/web/crowd_new-app-authorization.png

Figure 9.4. Creating a Nexus Crowd Application Authorization