Once the Atlassian Crowd plugin is installed, restart Nexus and login as a user with Administrative privileges. To configure the Crowd plugin, click on the Crowd Configuration in the Security section of the Nexus menu as shown in Figure 15.1, “Crowd Menu Link under the Security Section of the Nexus Menu”.
Clicking on the Crowd Configuration link will load the form shown in Figure 15.2, “Crowd Configuration Panel”. This configuration panel contains all of the options that need to be configured to connect your Nexus instance to Crowd for authorization and authentication.
The following sections outline all of the settings in the Crowd Configuration Pane.
The Access Settings section of the Crowd configuration is shown in Figure 15.3, “Crowd Access Settings”. This section contains the following fields:
- Application Name
-
This field contains the application name of a Crowd application. This value should match the value in the Name field of the form shown in Figure 15.8, “Creating a Nexus Crowd Application”.
- Application Password
-
This field contains the application password of a Crowd application. This value should match the value in the Password field of the form shown in Figure 15.8, “Creating a Nexus Crowd Application”.
- Crowd Server URL
-
This is the URL of the Crowd Server, this URL should be accessible to the Nexus process as it is the URL that Nexus will use to connect to Crowd's SOAP services.
- Authentication Interval
-
This is the number of minutes that a Crowd authentication is valid for. This value is in units of minutes, and a value of 30 means that Nexus will only require reauthentication if more than 30 minutes have elapsed since a previously authenticated user has accessed Nexus.
- Use Groups
-
If clicked, Use Groups allows Nexus to use Crowd Groups when calculating Nexus Roles. When selected, you can map a Nexus Role to a Crowd Group.
You can control the concurrency of connections to Crowd in the HTTP Settings section shown in Figure 15.4, “Crowd HTTP Settings”. If you have a high-traffic instance of Nexus, you will want to limit the number of simultaneous connections to the Crowd server to a reasonable value like 20. The HTTP Timeout specifies the number of milliseconds Nexus will wait for a response from Crowd. A value of zero for either of these properties indicates that there is no limit to either the number of connections or the timeout.
If your Nexus installation is connecting to Crowd via an HTTP Proxy server, the HTTP Proxy Settings section of the Crowd Configuration allows you to specify the host, port, and credentials for a HTTP Proxy server. The HTTP Proxy Settings section is shown in Figure 15.5, “Crowd HTTP Proxy Settings”.
The miscellaneous settings section shown in Figure 15.6, “Crowd Miscellaneous Settings”, allows you to configure settings
that control the name of the Single Sign-on cookie and the various keys
that are used to retrieve values that relate to authentication and the
auth token. This dialog is only relevant if you have modified optional
Crowd settings in your
${CROWD_HOME}/etc/crowd.properties. For more
information about customizing these options see the Atlassian
Crowd documentation.
