Resolution: Won't Fix
Affects Version/s: 3.3.1
Fix Version/s: None
The upgrade process allows incremental migration of select Nexus 2.x repositories by way of separate migration wizard executions.
When the Repository and Content migration option is selected, it will replace ALL user accounts in Nexus 3 with any and all of those in Nexus 2. There is no diff performed or reconciliation of user accounts.
The advantage is the implementation is simple and predictable.
The disadvantage is that if any changes/additions or deletes are made to user accounts in Nexus 3, these will be completely replaced with whatever is current in Nexus 2 at the time of the last migration.
- warn inside the upgrade wizard that migrating repository and content completely replaces all security in Nexus 3 and ask the user to confirm this action and press OK to continue and allow this ( do this even if this is the first time we think they are migrating content )
- come up with a less destructive migration option for user accounts
I do not want to migrate the users and roles from the old instance.
The idea is that after migration all existing roles and users assignments disappears on the new instance.
Just some clarifications.
Lets say, before migration my LDAP user has admin rights over the whole instance (OOS Nexus Version 3.2.1-01).
After migration, my LDAP user is NO LONGER ADMIN (OOS Nexus Version 3.2.1-01). I do not have any rights and I can't do anything.