Create an access token for your source control management (SCM) system

Azure DevOps

In Azure DevOps, create a personal access token:

1. Log in to your organization in Azure DevOps
2. From your home page, open your user settings
3. On the User Settings menu select Personal access tokens.
4. Click the + New Token button

5. Name your token and select All accessible organizations. Choose an expiry date for your token.

6. Select the scopes for this token to authorize for your specific tasks. For the full features of IQ SCM support enable Code: Read & Write and then select Create.

See this explanation for details of Azure DevOps scopes

7. When you're done, make sure to copy the token and save it somewhere safe for later use. Once you leave the generate token dialog it won't be shown again for your security.

Bitbucket Cloud

1. Log into Bitbucket Cloud.
2. In the bottom left click your avatar and choose Bitbucket settings.
3. In the Settings menu choose App passwords.
4. Click the Create app password button.
5. Choose a label for the token.
6. Click Create.
7. Save the app password somewhere safe. Once you leave or refresh the page you won’t be able to access it again.
8. Note that for Bitbucket Cloud the username for the account is also required.

See this article for more information on Bitbucket Cloud App passwords.

Bitbucket Server

1. Log into Bitbucket Server.
   
2. In the top right click your avatar and choose Manage Account.
3. In the left menu choose Personal access tokens.
4. Click the Create a token button.
5. Choose a name for the token.
6. Click Create.
7. Save the personal access token somewhere safe. Once you leave or refresh the page you won’t be able to access it again.
8. Note that for Bitbucket Server the username for the account is also required.

See this article for more information on Bitbucket Server Personal Access Tokens.

GitHub

In GitHub create a personal access token:

1. Log in to GitHub.
2. In the upper-right corner click your avatar and select Settings.
3. In the left menu click Developer Settings.
4. In the left menu click Personal access tokens.
5. Click the Generate new token button.
6. Save the personal access token somewhere safe for later use as once you leave the generate token dialog you will not be able to view it again.

See this explanation for details of GitHub scopes.

GitLab

In GitLab, create a personal access token:

1. Log in to GitLab.
2. In the upper-right corner click your avatar and select Settings.
3. On the User Settings menu select Access Tokens.
4. Choose a name and optional expiry date for the token.
5. Select the api and write_repository scopes
6. Click the Create personal access token button.
7. Save the personal access token somewhere safe. Once you leave or refresh the page you won’t be able to access it again.

Inform IQ Server about your Source Control Configuration

Enter your Root Organization Source Control Configuration

1. Login to Nexus IQ Server.
2. Navigate to the Root Organization.
3. Navigate to the Source Control configuration section.
4. Click to open the Source Control Configuration edit page.
5. Select your Access Token Provider.
6. Optional Enter your access token. This will be used as the default access token for all organizations if entered here.
   1.  Enter the username for the token if required by your specific SCM choice.
      
7. Enable or disable automated Pull Requests.
8. Enter your Default Branch (defaults to master)

Access tokens, username, enabling automated pull requests and the default branch can be overridden at the child organization and application levels.

Optional - Organization Source Control Configuration

Organizations may have their own source control provider, default credentials, enable automated pull request setting, and default branch by overriding these values at the organization level.

When a policy evaluation request comes in for any IQ application in that same organization, Nexus IQ for SCM will use the specified access token to communicate status information back to your repository.

Application Source Control Configuration

Applications may have their own source control provider, credentials, enable pull request setting and default branch by overriding these values at the application level.

Applications must specify a Repository URL to receive automated commit feedback and automated pull requests. The Repository URL is entered manually here.

Valid HTTP(S) and SSH repository URLs are accepted. Two formats are supported for SSH URLs: ssh://user@server/project-path.git and user@server:project-path.git.

On save, all SSH URLs are converted to the HTTPS format and the Repository URL will show the converted value.

With Automatic SCM Configuration turned on, the repository URL will be automatically discovered from the git project information and configured for the IQ application. Automatic SCM Configuration can be enabled via the configuration menu  in the toolbar.

Run a policy evaluation

Policy evaluations can originate from your CI environment, such as Jenkins, utilizing the IQ CLI directly or one of the Nexus IQ plugins provided for your respective CI system.  See this page for more information: https://help.sonatype.com/integrations/nexus-and-continuous-integration

You can also run a policy evaluation using the Nexus IQ command-line interface (CLI) directly, as described here: https://help.sonatype.com/integrations/nexus-iq-cli

The Nexus IQ client tooling will determine the commit hash and repository details for the given build and include that information in the policy evaluation request sent to the IQ server.