Migrate Polaris to the Black Duck domain

The Synopsys Software Integrity Group (SIG) is now Black Duck, and Polaris is the Black Duck Polaris® Platform. Follow the instructions on this page to migrate your Polaris tenant to the new Black Duck domain. We strongly recommend you complete this migration as soon as possible.

Before you run the migration

Before you run the migration, you will need to:

Each one of these steps is described in greater detail below.

Plan and schedule your migration

The migration can run for up to 15 minutes, but typically runs much faster. Running the migration won't impact any tests that are already in progress, and won't prevent you from running new tests. While the migration runs, users in your organization will not be able to sign into Polaris.

Running the migration will invalidate links in the welcome emails Polaris sends to new users. Please avoid inviting new users to Polaris during the 24-hour window before you run the migration.

Note: Once the migration is complete, Organization Administrators can reset a new user's password (My Organization > Users > select a user > Reset Password) to send the new user another email with a valid link they can use to sign into Polaris.

By now, you should have already completed the following actions:

Table 1. Polaris domain migration, key dates
Key date Milestones
September 15, 2025 Media types (used in Polaris APIs) that include "synopsys" will no longer function.
Tip: Several endpoints will be sunset on this date, too.

Versions of the Bridge CLI older than 3.6.0 will not function as expected. Upgrade to Bridge CLI 3.6.0 or newer to avoid failures.
September 30, 2025 Domains for Polaris (and its services) that include "synopsys" will stop functioning. Pipelines that haven't been updated will fail. Older versions of Black Duck® Code Sight™ will not function as expected. Tenants that haven't migrated to the Black Duck domain will be migrated automatically.
CAUTION: If you use single sign-on to manage access to Polaris, the automatic migration may prevent the users in your organization from accessing Polaris. Complete the migration by September 30, 2025 to avoid issues.

Running the migration

To run the migration, follow these steps:
  1. Go to My Organization > General.
    Note your Organization Name, listed near the top of the page. You'll need this in a later step.
  2. Under Black Duck Migration, select Start Migration.
    A confirmation appears.
  3. Enter your organization name and select Start Migration.
    Note: While the migration runs, users in your organization will not be able to sign into Polaris.
  4. When the migration is complete, select Reload.
    The Sign in page opens.
  5. Sign in to Polaris.

After you run the migration

After you run the migration, users in your organization can sign into Polaris from the new Black Duck URL:
Note: Other users in your organization who were signed into Polaris when the migration started will need to close Polaris and sign in again. They can still sign in to Polaris from the old URLs (https://polaris.blackduck.com, https://poc.polaris.blackduck.com, and https://eu.polaris.blackduck.com). During sign in, they will be redirected to the Black Duck domain automatically.

After you run the migration, you will need to:

Each one of these steps is described in greater detail below.

Generate new access tokens

While not required, we recommend you make new access tokens and use them when you update your pipelines and API scripts. See Make an access token for more information.

Update your pipelines

Minimally, in addition to replacing the token(s) your pipelines use, please update the Polaris server URL your pipelines reference.

See Complete List of Bridge Arguments > Polaris for more information.

Important: Older versions of the Bridge CLI will stop functioning on September 15, 2025. Upgrade Bridge CLI to version 3.6.0 or newer before September 15 to avoid failures.

Update API scripts

In addition to replacing the token(s) your API scripts use, please update:

Upgrade Code Sight

If you use Black Duck® Code Sight™ with Polaris, we recommend you upgrade Code Sight after you run the migration.
  1. Follow the instructions in Black Duck Community to uninstall older versions of Code Sight and then install the latest version of Code Sight: HOW TO: Migrating existing Synopsys Code Sight users to the new Black Duck Code Sight.
  2. Open the Polaris tab (found in Code Sight's Authentication preferences).
  3. Replace the token Code Sight uses and update your Polaris server URL:

Update your bookmarks

We recommend you update your bookmarks to Polaris after you perform the migration.

After you sign into Polaris on the new Black Duck domain, bookmarks to pages in Polaris (that use the old domain) may direct you to a Sign In page. If this occurs, follow these steps:

  1. Enter your Email Address and select Next.
    The Portfolio page opens.
  2. Select your bookmark again.
    Now, whenever you select an old bookmark (a bookmark that uses the old domain), you will automatically be redirected to the Black Duck domain.
    Important: Your browser's cookie settings may prevent automatic redirection from working as expected. Each time you clear your browser's cookies, you will need to repeat these steps. Additionally, redirection will only work until September 30, 2025; update your bookmarks before then to avoid issues.
    Tip: Most browsers allow you to export your bookmarks to a text file, which can be modified in a text editor (think, find and replace), and reimported.

Need support?

To request support, follow these steps:
  1. Select the Help icon (near the upper-right corner of Polaris).
    The search panel opens.
  2. Select Need additional help or support? (near the bottom of the panel).
    The How Can We Help You? page opens.
  3. Select Submit a Case.
  4. When Black Duck Community opens, create a support case.
    See Submit a support ticket for more information.