Setting up an AppScan Presence to scan an Azure DevOps repository

Configure an AppScan Presence to connect to Azure DevOps repositories using a personal access token (PAT) scoped to your Azure DevOps organization.

Before you begin

  • Ensure that you have access to an Azure DevOps organization and permission to access the repositories you plan to scan.
  • Ensure that your Azure DevOps organization permits you to create a PAT with the required scopes.
  • Create and install an AppScan Presence on a private network with access to Azure DevOps.

About this task

The Azure DevOps server does not have to be publicly accessible. You must have network access to the server and permission to access its repositories.

Procedure

  1. Create a PAT for your Azure DevOps organization.
    1. Sign in to your Azure DevOps organization.
    2. Open User settings and select Personal access tokens.
    3. Select + New Token.
    4. Enter a name, select the organization that contains your repositories, and set an expiration date.
    5. Under Code, select Read.

      This is the minimum PAT scope required for scanning.

    6. Select Create and copy the token immediately.

      Store the token securely. Azure DevOps does not display its value again. For more information, see Use personal access tokens.

  2. Open git_connect_settings.json in the AppScan Presence installation directory.
  3. In the GitConnectOptions section, configure the Azure DevOps connection.
    ParameterDescriptionExample
    GitServerNameA name for the Azure DevOps server.Azure DevOps
    GitConnectUrlThe HTTPS URL of the web application exposed by this Presence.https://my-presence-host-fqdn:443
    GitPlatformDomainThe URL of the Azure DevOps server.https://dev.azure.com
    GitPlatformTypeThe repository provider.AzureDevOps
    AccessTokenThe PAT created for the Azure DevOps organization.personal-access-token
    OrganizationNameThe name of the Azure DevOps organization.organization-name
    ActiveEnable the Azure DevOps connection. The default is false.true
    ProxyIf a proxy is required to connect to Azure DevOps, uncomment this parameter and enter the proxy details.127.0.0.1:8888
  4. Configure an HTTPS endpoint in the Kestrel section of git_connect_settings.json.

    HTTPS is required. For example, use https://*:443, or your secure port, as the endpoint URL. Use the same port in GitConnectUrl.

    For endpoint and certificate configuration, see Configure endpoints for the ASP.NET Core Kestrel web server.

  5. Save the configuration file, then start or restart the Presence.

    Logs are written to the console and to files in the logs folder in the Presence installation directory.

What to do next

To scan a repository using the Presence, select Azure DevOps as the provider, select the configured Presence, and select Authorize Presence. Then select the repository and branch and complete the scan configuration.

To connect multiple repositories, see Onboarding multiple repositories for scanning.