Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-11941

Custom roles starting with 'nx2' are not applied to users during NX2 to NX3 upgrade

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 3.1.0, 3.2.0
    • Fix Version/s: None
    • Component/s: Migration
    • Labels:
      None
    • Environment:
      Chrome, FF MacOSX

      Description

      While testing on NXRM2, I created a privilege for All Repositories - All (npm) called "nx2migrationtest". Then I created a role called "nx2migrationtest" and gave it those privileges. Then I created a user ("testuser" for the sake of this example) and gave it that role.
      I then Upgraded NX2 to NX3.
      After success, I noticed all 3 of these seemed to have Upgraded over, however, "testuser" had no role defined.
      See attached screens and vid for exact (post-Upgrade) results.

      After further analysis, as far as I can tell this issue seems limited to items with "nx2" in the front. The same scenario with items named "migrationtestnx2" was successfully Upgraded.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jtom Joe Tom
            Last Updated By:
            Peter Lynch Peter Lynch
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Date of First Response:

                tigCommentSecurity.panel-title