Preparing to Migrate

1. Identify your current Nexus repositories
2. Cleanup repositories
3. Identify Nexus references
4. Identify Generic IDs
5. Identify usage of Anonymous access
6. Identify Security Groups

In preparation to migrate from Nexus to JFrog Artifactory, there are a few key steps that will help to ensure a smooth start to your migration process. Some of these steps will require team lead or possibly LL6 access. Team members should feel free to help with preparation as they are able.

Identify your current Nexus repositories

Knowing which repositories you will be migrating is the best starting place. Having this documented and ready to compare against any lists that the Nexus team has also generated will ensure that nothing is missed.

In addition, at this time, please identify any repositories that may have been previously requested, but are now unused. You can request that these repositories be removed via an IT Connect ticket: here. Choose Nexus(22770) as the application and include any repositories that can be removed prior to the migration.

Figure 1. Requesting a task in IT Connect for Nexus

Cleanup repositories

Look through your repositories and see if there is any old data that can be cleaned up. Releases or dependencies that are no longer needed. For Maven/Gradle, do not worry too much about Snapshot repositories, these will not be migrated, but rather fresh Snapshot repositories created in place where needed.

Identify Nexus references

Look through your codebase/IDE/scripts for references to Nexus. Document these, so that updating them will be an easier task in the future. Most repository references will be a straightforward replacement with a new JFrog Artifactory URL.

Identify Generic IDs

If your project uses a generic id, make a note of this as well. JFrog Artifactory does not support username/password authentication for it's tools. Sign on to the web UI is via SAML SSO out of Azure AD. If your generic id can perform sign-ons via Azure AD, you should be able to generate your own Access token, otherwise it will require an IT Connect ticket: here, choosing the JFrog(7020656) application. NOTE: Make sure your generic ID belongs to "ENTP-GITHUB-FORD-GENERIC" FIM group, if not, follow the steps in Access for Generic (Proxy) ID and request access.

Figure 2. Requesting a task in IT Connect for JFrog Platform

Identify usage of Anonymous access

Since JFrog Artifactory is open to the outside world, it will not support anonymous access. Identify if and where your CI/CD process is using anonymous access and make note of this. It will need to be updated to use an authenticated user.

Identify Security Groups

You will want to identify and document the security groups that you are currently using in Nexus to manage access to your repositories. These can be found in EIdM. There are two ways to identify them. The lefthand menu in EIdM has two options under "Security Groups (SGs)." "My SGs" which is Security Groups you are an owner of, and "My SG Memberships" which is Security Groups you are a member of. Both of these are a good place to start looking for the correct Security Groups.

Figure 3. Locating Security Groups you are associated with

Once, you are in the correct place, you will see a list of Security Groups, with their owners and descriptions. Locate your Nexus Security Groups. They will very likely be in the form of [Team Identifier]-NEXUS-[Role]. Make sure the ownership and members are up to date. These groups will be reused by default to provide access in JFrog Artifactory.

Figure 4. Nexus Security Groups for the SDE Team