You must be signed in as a super administrator for this task.
With Security Assertion Markup Language (SAML), your users can sign in to enterprise cloud applications with their Google Cloud credentials.
Set up SSO via SAML for Veracode
Step 1: Set up Google as a SAML identity provider (IdP)-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
-
Click Add appSearch for apps.
- Enter Veracode in the search field.
- In the search results, hover over the Veracode SAML app and click Select.
- On the Google Identity Provider details page:
- Copy and save the SSO URL and the Entity ID.
- Download the Certificate.
- Click Continue.
- On the Service provider details page, keep the default values.
- Click Continue.
- On the Attribute mapping page, click the Select field menu and map the following Google directory attributes to their corresponding Veracode attributes:
Google directory attribute Veracode attribute Basic Information > First Name firstname Basic Information > Last Name lastname Basic Information > Primary Email email -
(Optional) To enter group names that are relevant for this app:
- For Group membership (optional), click Search for a group, enter one or more letters of the group name, and select the group name.
- Add additional groups as needed (maximum of 75 groups).
- For App attribute, enter the corresponding groups attribute name of the service provider.
Regardless of how many group names you enter, the SAML response includes only groups that a user is a member of (directly or indirectly). For more information, go to About group membership mapping.
- Click Finish.
- Open a new incognito browser window.
- Sign in to https://analysiscenter.veracode.com/ with your organization's Veracode administrator account.
-
In the Veracode home page, click to open Settings.
-
Click Admin SAML.
-
In the Issuer field, enter the Entity ID you copied in step 1.
-
In the IdP Server URL field, enter the SSO URL you copied in step 1.
-
In the Assertion Signing Certificate field, upload the certificate you downloaded in Step 1.
- Click Save.
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
- Select Veracode.
-
Click User access.
-
To turn a service on or off for everyone in your organization, click On for everyone or Off for everyone, and then click Save.
-
(Optional) To turn a service on or off for an organizational unit:
- At the left, select the organizational unit.
- To change the Service status, select On or Off.
- Choose one:
- If the Service status is set to Inherited and you want to keep the updated setting, even if the parent setting changes, click Override.
- If the Service status is set to Overridden, either click Inherit to revert to the same setting as its parent, or click Save to keep the new setting, even if the parent setting changes.
Note: Learn more about organizational structure.
-
(Optional) To turn on a service for a set of users across or within organizational units, select an access group. For details, go to Use groups to customize service access.
- Ensure that your Veracode user account email IDs match those in your Google domain.
Note: Veracode supports IDP initiated flows only. SP initiated flows are not supported.
-
Sign in to your Google Admin console.
Sign in using an account with super administrator privileges (does not end in @gmail.com).
-
In the Admin console, go to Menu AppsWeb and mobile apps.
- Select Veracode.
- At the top left, click Test SAML login.
Veracode should open in a separate tab. If it doesn’t, use the information in the resulting SAML error messages to update your IdP and SP settings as needed, then retest SAML login.
You should be automatically redirected to your Veracode account.
Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.