For repository content the Basic auth realm name of nexus 2 when accessing content is "Sonatype Nexus Repository Manager".
The Basic auth realm name of nexus 3.0.0 is "Sonatype Nexus".
We have seen at least one instance of breakage when changing realm names:
When a user migrates from Nexus 2 to Nexus 3, this realm name change could cause builds using IVY based deployments ( SBT, ANT ) to start failing. Fixing this on the client side could require a huge set of ivysettings.xml changes in source control or build jobs. ivysettings.xml fils can contain sections with credentials such as
While 'realm' is an optional configuration attribute - even if it is left out, then credentials will not be found that match the realm name and authentication fails with 401 like it does when the realm name is specified but does not match exactly the realm name sent in the Nexus WWW-Authenticate header.
Should the Nexus 3 realm equal the Nexus 2 realm name?