Overview
The Synopsys Software Integrity Group (SIG) is now Black Duck, and Coverity on Polaris is Black Duck® Coverity® on Polaris. Follow the instructions on this page to migrate your Coverity on Polaris platform to the new Black Duck domain.
Update your allow list
To ensure Coverity on Polaris continues to function as expected, update your allow list.
Plan and schedule your migration
See critical dates below for when you will need to migrate to the Black Duck domain.
| Key date | Milestones |
|---|---|
| January 13, 2026 | Domains for Coverity on Polaris (and its services) that include "synopsys" will stop functioning. Pipelines that haven't been updated will fail and certificate errors will prevent users from accessing Coverity on Polaris in browsers. CAUTION: If you use single sign-on to manage access to Coverity on Polaris, the automatic migration may prevent the users in your organization from accessing Coverity on Polaris. Complete the migration by January 13, 2026 to avoid issues.
|
| March 24, 2026 | Media types (used in Coverity on Polaris APIs) that include "synopsys" will no longer function. |
If you use single sign-on
If you use SSO, the Organization Administrator must create a new SAML 2.0 Identity Provider integration or update the settings to the Black Duck URL. See Migrate SAML Integration to Black Duck for instructions.
If you use local authentication
If you use local authentication, you can sign into the Black Duck domain ("https://<your companyID>.cop.blackduck.com") with the same email/password used for Synopsys.
If you use Jira integration
If you use Jira integrations, the Organization Administrator must update Jira settings to the Black Duck URL. See Migrate Jira Integration to Black Duck for instructions.
If you use Coverity on Polaris CLI, update your Server URL
If you use Coverity on Polaris CLI and already have a default or central configuration, you will need to update your polaris.yml serverURL value with your new Black Duck domain URL.
If Coverity on Polaris CLI does not have a central or default configuration, use your new Black Duck domain URL when asked for serverURL.
You can also change the server URL with the environmental variable POLARIS_SERVER_URL.
If you use Jenkins integrations
You will need to migrate to Black Duck Coverity on Polaris Jenkins plugin version 2.0.0 or newer. Carefully review documentation including what you need to do before you begin migration (Migrating your Jenkins integration to Black Duck) .
If you use Azure integrations
You will need to migrate to Black Duck Coverity on Polaris Azure extension version 2.0.0 or newer. Carefully review documentation including what you need to do before you begin migration (Migrating your Azure DevOps integration to Black Duck) .
Update Bookmarks
After you migrate to Black Duck, update your bookmarks. Bookmarks from either domain will continue to work (unless you have migrated your Azure SSO) but users may need to authenticate multiple times and on January 13, 2026 “synopsys.com” bookmarks will stop working. Update your bookmarks before January 13, 2026 to avoid issues.
Tokens
API tokens work with both domains. However, when you generate JWT tokens from these API tokens, each JWT token will only work with the specific domain it was created for.