Onboarding CSC Global DNS

Prerequisites

Before you configure the CSC Global DNS integration in AppViewX, ensure that an API user is created in CSC DomainManager with DNS zone read and write permissions. AppViewX requires these settings to perform Domain Control Validation (DCV) or ACME DNS-01 challenge validation by managing DNS records through the CSC DomainManager API v2.

Before you configure the CSC Global integration in AppViewX, ensure the following prerequisites are met in your CSC DomainManager account.

API User Account

Create or designate an API user in CSC DomainManager. AppViewX uses this account to authenticate against the CSC DomainManager API v2 endpoint. Obtain the following credentials for this user:
  • API username
  • API key
  • CSC DomainManager API v2 base URL
Note: Contact your CSC Global account representative to request API user provisioning if one does not already exist.

Required API Permissions

The API user that you configure for AppViewX integration must have DNS zone read and write permissions in CSC DomainManager. These are the only permissions required for DNS-based DCV automation.
Table 1. CSC DomainManager API permissions required for AppViewX integration
Category Action Access type
DNS (CSC Basic DNS) Manage DNS records add, update, and purge records; check the status of updates; cancel failed updates Write
Retrieve details of DNS updates Read only
Retrieve DNS records Read only
Retrieve DNS Zones permission Read only
Note: Grant only the DNS zone read and write permissions listed above. Permissions for Domains, DS Records, Digital Certificates, Orders, Reference Information, and Token Refresh are not required for DNS record creation and should not be granted, following the principle of least privilege.

Network Connectivity

Ensure that AppViewX can reach the CSC DomainManager API endpoint over HTTPS (port 443). The API base URL follows this pattern:
https://api.cscglobal.com/

If your AppViewX deployment is behind a firewall or proxy, ensure that outbound HTTPS access to the CSC DomainManager API domain is permitted.

DNS Zone Availability

The domains for which DCV will be performed must be managed under the CSC DomainManager account associated with the API user. During DNS automation, AppViewX retrieves the hosted zones list and validates that the required zones exist before it creates DNS TXT records.
Note: CSC Basic DNS must be enabled for the domains in scope. If your domains use an external DNS provider through CSC, refer to that provider's onboarding documentation instead.

Configuring CSC Global DNS

  1. Go to Menu > CERT+ > ADMINISTRATION > DCV Management > Manage DDI services > Add new vendor.
    The Select Vendor page appears.
  2. On the Select Vendor page, select CSC Global.
  3. On the Vendor Configuration page, under General, enter or select the required information.

    The following table describes the fields in this section:

    Field Description
    *Name Enter a unique name to identify the vendor account that you are configuring.
    Description Enter a description for this vendor configuration. This field is optional.
    Data center Select a data center from the dropdown list.
    *: Mandatory fields
  4. Under Credentials, enter or select the required information.

    The following table describes the fields in this section:

    Field Description
    *Auth Type Select the authentication method. API Key is selected by default for CSC Global.
    *URL Enter the CSC DomainManager API v2 endpoint URL in HTTPS format.

    Example: https://api.cscglobal.com/

    *Key Displays Authorization as the default header key name. This value is pre-populated and typically does not require changes.
    *Value Enter the API key value generated for the CSC DomainManager API user that is configured for AppViewX integration.
    *Add to Specifies where the API key is sent. Header is selected by default and is required for CSC Global.
    *Custom Header Enable this toggle to add a custom header to the API request. This setting is turned on by default for CSC Global.
    *: Mandatory fields
  5. Under Custom Header Config, enter the custom header details.

    The following table describes the fields in this section:

    Field Description
    apiKey The custom header key name is pre-populated as apiKey. This is the header that CSC Global uses to pass the API key in requests.
    Value Enter the API key value that corresponds to the apiKey header. This value is provided by CSC Global when the API user is provisioned.
  6. Turn on Config sync to enable vendor parsing.
  7. Under Configurations, turn off the Enable Advanced Config toggle.
  8. Select Next, review the summary, and then select Finish.
    A Vendor configuration saved successfully confirmation message appears.

Validating the Vendor Configuration

  1. On the Integration Hub page, locate the configured vendor tile.
  2. Confirm that a green check mark (✔) appears on the tile. This indicates the vendor is active and reachable.
  3. Select the View status icon on the tile to open the Vendor Status Log dialog for the vendor.
  4. Verify that the Authentication entry shows a Success status with a recent timestamp.