Nexus Repository 2 vs. Nexus Repository 3 Feature Equivalency Matrix

Server Settings

Yes

These are settings under Administration → Server in Nexus Repository 2

Security

Yes

See Access Control and User Authentication

Local User Accounts

Yes

Privileges

Yes

Names may change on upgrade from Nexus Repository 2 to 3. Note that transitive group privileges are implemented differently in Nexus Repository 2 and 3:

In Nexus Repository 2, when a user is given a privilege to a group repository, then that user will also have that privilege to all transitive members of that group repository.This permission access applies even if the HTTP requests are sent directly to the member repositories rather than the group repository.As repositories are added to or removed from a group, the user may gain or lose access to those individual repositories. (See more inthis Nexus Repository 2 support article.)

In Nexus Repository 3, when a user is given a privilege to a group repository, then that user will also have that privilege to all transitive members of that group repository only when their request is directed to the group repository. Direct requests to indvidual member repositories will only work if the user is given explicit permission to the individual repository.

The Upgrade Wizard does not detect this difference. After upgrading from Nexus Repository 2 to 3, you may need to manually assign privileges for individual repositories to a subset of users.

Roles

Yes

Maven Repositories

Yes

Proxy Repository of maven.oracle.com

Yes

See the KB article to configure

Browse Remote

No

Repository Targets

Yes

Maps to content selectors

Manual Routing Rules

Yes

See Routing Rules

Maven Settings

No

Automatic Routing

No

We will consider similar optimization features like this in the future as warranted.

Smart Proxy

Yes

See Content Replication

Procurement

Yes

Procurement is deprecated. The Sonatype Repository Firewall solution provides a comprehensive set of features aimed at managing risk in your repository.

Staging

Yes

Nexus Repository 2 Staging is replaced with component tagging to manage workflow.

See Staging

Custom Metadata

Yes

Nexus Repository 3 can associate arbitrary data with any component in any repository format via its tagging feature. However, there is no automated way to migrate Nexus Repository 2 custom metadata.

YUM Repositories

Yes

p2 and p2 Update Site Repositories

Yes

RubyGems Repositories

Yes

PyPI Repositories

Yes

npm Repositories

Yes

NuGet Repositories

Yes

NuGet API Keys

Yes

Bower Repositories

Yes

Site Repositories

Yes

Renamed as the raw repository format in Nexus Repository 3

System Feeds

No

We have no plans to upgrade System Feeds as the data is specific to the instance where it was generated. Near equivalent functionality is available through auditing and webhooks.

Branding

Yes

The branding configuration is not be upgraded automatically. Nexus Repository 3 uses the branding capability.

REST API

Yes

Nexus Repository 2 REST APIs are not compatible with Nexus Repository 3.

See the Nexus Repository 3 REST API documentation.

Non-Sonatype Repository Plugins

No

Nexus Repository 2 plugins are not compatible with Nexus Repository 3 OSGI bundle architecture

SSL Certificates

Yes

SSL certificates trusted in the UI will be upgraded, but not all of them apply. Review trusted certificates after the upgrade. The wizard does not migrate the certificate that Nexus Repository uses for its own HTTPS connection.

Analytics

No

LDAP

Yes

Nexus Repository OSS Servers

Yes

Nexus Repository Pro (Enterprise) Servers

Yes

Individual LDAP Server configurations will be upgraded. Backup Mirror servers will not be upgraded.

Mapped Users and Roles

Yes

Atlassian Crowd

Yes

Verify the Crowd application is configured to accept connections from Nexus Repository 3

Mapped User and Roles

Yes

User Token

Yes

See the Prerequisites for Upgrading from Nexus Repository 2 to Nexus Repository 3 for information on how to include pre-existing user tokens from your Sonatype Nexus Repository 2 instance when upgrading to Nexus Repository 3.

IQ Server Configuration

Yes

The wizard clones the IQ Server configuration. The quarantine data is cloned to work with repositories upgraded to Nexus Repository 3.

Repository Health Check Analysis (RHC)

Yes

Instances with the Sonatype Repository Firewall solution enabled do not see Repository Health Check.

Learn more about Sonatype Repository Firewall

RUT Auth Realm

Yes

This is not upgraded automatically as it is a security concern when enabled.

Configure this manually inside Nexus Repository 3 when you are confident that Nexus Repository 3 access is protected.