Nexus Repository Professional Features

Sonatype Nexus Repository Pro users receive access to our world-class support organization. This highly skilled group works with you to resolve issues encountered while using the product.

Details are found in our Support Policy.

Sonatype invests in every enterprise customer through our Customer Success team. This team is unique in that they proactively and continuously collaborate with you to ensure you derive ongoing value from your investment.

Ask them about training in repository management for your teams and providing a Repository Health Check to perform a details review of your development while providing guidance to help your organization mature.

Nexus Repository is mission-critical for your business. Highly available (HA) deployments protect your business in the event of disaster or outages. We include a growing list of resilient deployment architectures and recovery tools to protect your investment.

Nexus Repository Pro protects your data from risk while reducing your recovery time and meeting recovery point objectives.

Nexus Repository Pro integrates with many identity providers for centralized identity management. Using SAML, Nexus Repository acts as a service provider that receives users' authentication and authorization information from external identity providers.

Sonatype Nexus Repository Pro’s user token feature establishes a two-part token for the user. Usage of the token acts as a substitute method for authentication that would normally require passing your username and password in plain text.

User tokens reduce the risk of exposing your enterprise credentials when using external tools such as CI build services, automation tools, development environments, and scripting with the REST APIs. Administrators may reset and rotate keys from within the Nexus Repository as part of their security policies.

Teams today rarely work from a single location, so why should artifacts be stuck in one? Content replication allows you to make artifacts readily available across distributed teams. With content replication, you can manage what binaries are copied from one instance and pre-emptively pulled via HTTP to other instances. Here's how it works:

Nexus Repository Pro provides Staging and Build Promotion capabilities to ensure the integrity and quality of software components before they are released. This feature allows organizations to implement controlled workflows for validating, testing, and promoting artifacts through different lifecycle stages.

With staging, users can temporarily hold newly published components in an isolated repository before making them available in a release repository. This approach helps prevent the accidental deployment of incomplete or unverified artifacts. Build promotion further enhances this process by enabling teams to transition artifacts from one repository to another based on validation criteria, ensuring that only approved versions reach production.

By integrating Staging and Build Promotion into their software development lifecycle, teams can enforce quality gates, reduce deployment risks, and maintain better governance over their repositories.

For more details, refer to the Staging documentation.

Nexus Repository Pro includes a Tagging feature that allows users to assign metadata tags to repository components, simplifying asset organization, tracking, and management. By applying tags, teams can efficiently categorize and reference specific artifacts across different repositories, enabling better version control and lifecycle management.

With Tagging, users can:

This feature is particularly useful for managing artifacts in large-scale environments, where clear identification and traceability are essential for governance and compliance. The implementation is highly flexible to include any metadata you need to track with the components.

For more details, refer to the Tagging documentation.

Importing and exporting repositories is a common enterprise capability to move a large number of components between repositories or repository managers. Use cases to utilize import and export include:

These tasks keep track of the last run results and if run again, they will skip files that were processed previously. These tasks work with HA-C setup.

A temporary file system location is needed for these tasks to export to and import from. Please also ensure the Sonatype Nexus Repository instance running the task has sufficient disk space for export and blob storage for import before running this task to avoid disk full issues.

The Google Cloud Storage Blob Store allows assets to be stored in a Google Cloud Storage (GCS) bucket. Nexus Repository Pro can take advantage of the storage features that Google Cloud provides, such as redundancy options, configurable storage classes, and access control when running within the Google Cloud environment.

The Azure Blob Store allows assets to be stored in an Azure Storage Account container. Nexus Repository Pro can take advantage of the storage features that Azure provides such as replication, configurable performance profiles, and access control when running from within the Azure cloud.

A group blob store combines multiple blob stores to function as a single location for your repositories. Members of the group can be added or removed. Fill Policies are selectable algorithms that determine to which group member a blob is written. These features significantly increase the flexibility customers have in using and upgrading their storage. More information can be found in the Storage Guide.

Change repository blob store is a task that allows changing the blob store of a given repository. It moves the blobs from the chosen repository to a different blob store.

Some common use cases to utilize the Change Repository Blob Store task:

Nexus Repository Pro supports Deployment to Group Repositories for npm and Docker registries, allowing users to publish artifacts to a group repository. When configuring the group, a hosted repository is set to store published artifacts. This feature simplifies artifact management by enabling deployment to a single endpoint while ensuring that the artifact is available to all member repositories within the group.

This capability enhances repository management efficiency and is particularly beneficial for teams that require centralized artifact deployment while maintaining access through a unified repository group.

Nexus Repository users can automatically identify open-source security risks at the earliest stages of their DevOps pipeline. Specifically, the RHC feature empowers software development teams with important capabilities:

Atlassian Crowd is a single sign-on and identity management product that many organizations use to consolidate user accounts and control which users and groups have access to which applications. Atlassian Crowd support is a feature preinstalled and ready to configure in Nexus Repository Pro. Nexus Repository contains a security realm that allows you to configure Nexus Repository to authenticate against an Atlassian Crowd instance.