Onboarding Micetro DNS

Prerequisites

Before you configure the Micetro DNS integration in AppViewX, ensure that a dedicated API user account is created in Micetro with the correct role-based permissions. AppViewX uses Basic Authentication to connect to the Micetro REST API and perform DNS TXT record management for Domain Control Validation (DCV) or ACME DNS-01 challenge validation.

Before you configure the Micetro integration in AppViewX, ensure the following prerequisites are met in your Micetro environment.

Create a Dedicated API User Account

Create a dedicated local user account in Micetro that AppViewX will use to authenticate against the Micetro REST API. Using a dedicated account rather than a shared administrator account limits the blast radius of a credential compromise and makes audit logs easier to interpret.
To create a user account in Micetro:
  1. Sign in to the Micetro web application.
  2. Go to Admin > Configuration > Users.
  3. Select Create user.
  4. Enter a username (for example, appviewx-dcv), set a strong password, and select Save.
  5. Obtain the following credentials for the new account:
    • Username
    • Password
    • Micetro Central hostname or IP address
Note: Micetro supports local users and externally managed users (for example, Active Directory). AppViewX requires a local Micetro user account. External directory users that are not synchronized as local Micetro users cannot be used for API authentication.

Minimum Required Access and Permissions

The Micetro integration account must be able to discover the intended DNS view and perform record-level changes in the approved zones. The AppViewX API user must be assigned to a role that includes the following permissions.
Table 1. Minimum required permissions for Micetro DNS integration
Group Permission
DNS zones List (or view) zone
DNS zones View zone history
DNS zones Edit apex records
DNS zones Edit other records
Note: When the same zone name exists in both the AD internal view and the public external view, create a service account with the specific view required. For example, for DCV Management use a service account with the external view, or for ACME DNS challenge validation use a service account with the internal view.

Create and Assign the Role in Micetro

If no suitable role exists, create a custom role in Micetro and assign the AppViewX API user to it.

To create and assign the role:

  1. Go to Admin > Configuration > Roles.
  2. Select Create. The Create role dialog box appears.
  3. Enter a name (for example, AppViewX-DCV) and an optional description.
  4. Select the Access tab and enable the permissions listed in the tables above.
  5. Select Save.
  6. Open the role you created, select the Users tab, and add the AppViewX API user account.
  7. Select Save.
Note: When you enable a permission in Micetro, all dependent permissions are automatically enabled to avoid access issues. An information icon in the upper-right corner of the dialog summarizes the enabled dependent permissions.

API Access Requirements

Ensure that the Micetro Central REST API is accessible from AppViewX. The following table describes the access requirements:
Table 2. Micetro API access requirements
Access type Requirement
REST API access Required. The Micetro Central REST API must be enabled and reachable from AppViewX over HTTPS (port 443) or HTTP (port 80).
Authentication method Basic Authentication (username and password).
GUI access Not required for AppViewX integration.

Network Connectivity

Ensure that AppViewX can reach the Micetro Central server over HTTPS (port 443) or HTTP (port 80). The API base URL follows this pattern:
https://<micetro-central-hostname-or-ip>
If your AppViewX deployment is behind a firewall or proxy, ensure that outbound access to the Micetro Central host on the required port is permitted.
Note: During DNS automation, AppViewX retrieves the hosted zones list and validates that the required zones exist before it creates DNS TXT records.

Configuring Micetro 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 Micetro.
  3. 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 Displays Basic Auth as the authentication method selected by default for Micetro.
    *URL Enter the Micetro Central API endpoint URL in HTTPS or HTTP format.
    Example: https://<micetro-central-hostname>
    Note: The API URL is the same as the Micetro Central hostname URL.
    *Username Enter the username of the Micetro local user account configured for AppViewX integration.
    *Password Enter the password of the Micetro local user account configured for AppViewX integration.
    *: Mandatory fields
  5. Turn on Config sync to enable vendor parsing.
  6. Turn off Sync IPAM and Sync DNS, as these options are not required for DNS validation.
  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.