Migrate SAML Integration to Black Duck

With the transition from Synopsys to Black Duck, you will need to update your SAML integration to Black Duck.

Two options are available:

Create a new SAML Identity Provider integration (safest option).
Update your SAML Identity Provider configuration.

Note: After you change the SAML configuration to the new domain, it is recommended to use the new domain. If you use Azure for SSO, after migration, users must login to new domain only. You will get an error when attempting to login to old domain.

Create a new SAML Identity Provider integration

Reset your whole SAML integration by removing your current integration and adding a new SAML integration.

Uninstall current SAML integration.
1. Go to Identity Provider and sign in as admin.
2. Find integration and deactivate/delete.
Follow directions here: Integrating a SAML 2.0 Identity Provider. You will need to repeat all the steps you did in the original integration.

Note: This will cause disruption in SSO since existing users will not be able to sign in until configuration is complete, usually about an hour.

Update your SAML Identity Provider configuration

You can use this method if your metadata has not expired. You do not need to change anything in Coverity of Polaris.

Sign in to your SAML identify provider as an admin.
Find Coverity on Polaris.
1. For example, for Okta, go to Dashboard > Applications.
2. For OneLogin, go to Applications > SAML Test Connection (IdP) > Configuration.
Go to existing configuration > SAML Settings and click edit.
Change domains to your new Black Duck domains ("polaris.synopsys.com" to "cop.blackduck.com").

In the Okta example below, update the first two lines.

In the OneLogin example below, update four URLs:
Save changes.

Note: After you change your SSO, remember to update your bookmarks to the Black Duck domain.