A role in Nexus 2 may be assigned a repository view privilege - an example entry would take the form:
<repoid> - (view)
Where repoid is replaced with the actual repository identifier. Example:
company_repo-repo - (view)
When such a role is migrated to Nexus 3 by the upgrade process, this view privilege is omitted, resulting in users assigned that role to not be able to browse the contents of the affected repositories.
In attached screenshots the "somegroup" role has view and read privileges to the "somegroup" group repository.
After upgrade, the "somegroup" role only has a read privilege. It should also have a "nx-repository-view-<format>-somegroup-browse" privilege for this group.
If you have a small number of affected roles, then assign the missing privilege manually to the affected Nexus 3 roles.
The missing privilege takes the form of this naming pattern:
Or you can assign view privileges to all repositories by using:
If you have a large number of affected roles, then we advise waiting until we fix this issue before upgrading.