Firewall Repository Management

The integration between Nexus Repository Manager and IQ Server provides access to detailed Repository Results identifying components that represent potential risk to the components and applications your teams are developing it. In addition to this repository intelligence, you are able to perform a variety of actions based on these results, including the ability to waive violations, as well as manage labels. This section provides instructions for managing the repositories, an overview of repository results, and guidance when managing roles and users.

The features discussed in this section require Nexus Repository Manager Pro and IQ Server with the following licenses: Repository and Firewall.

Managing Repositories

The creation, modification, and deletion of repositories is managed via Nexus Repository Manager. However, IQ Server also displays information about any connected repositories.

To view this information:

  1. Click the Organization & Policies button  located in the IQ Server toolbar.
  2. Click on Repositories, located in the sidebar on the left side of the screen. The Configuration tab is displayed, as shown in the figure below.

Details on repositories include:

  • The public id of the repository
  • The instance id of the Nexus Repository Manager hosting the repository
  • The current audit-enabled state of the repository

Clicking the Remove Repository  (trash can) icon allows you to delete the repository after you confirm the deletion in a dialog.

This action affects only IQ Server, not Nexus Repository Manager. While the repository entity and its data are permanently removed from IQ Server, the repository in Nexus Repository Manager remains unchanged.

The deletion of a repository in IQ Server will NOT be replicated to Nexus Repository Manager.

Managing User Roles

The Repositories page, accessible from the sidebar of the Organization & Policies area, lets you adjust access settings for repository evaluation results. The process is the same as managing roles and permissions for organizations and applications on IQ Server. Through role assignments, you have the ability to grant users different permissions for repository evaluation results without granting them access to organizations and applications. For example, to grant a user the ability to view repository results, you assign the user to a role with View IQ Elements permission. To edit repository results, you assign the user to a role with Edit IQ Elements permission.

Any role assignments made at the Root Organization level are inherited automatically by Repositories. However, if you set a role in Repositories, the Root Organization is unaffected.