MID Server Field Missing in Manage Endpoints and New Record Forms - VCF Plug-In for ServiceNow
search cancel

MID Server Field Missing in Manage Endpoints and New Record Forms - VCF Plug-In for ServiceNow

book

Article ID: 453754

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

This article addresses cases where the MID server field is not visible within the VCF Plug-In for ServiceNow "Manage Endpoints" or "New Record" forms, preventing the configuration of automation endpoints.

Symptoms:

  1. Users are unable to see the MID server field in the "Manage Endpoints" section.
  2. The MID server field is absent when creating a "New Record" for endpoints.
  3. ServiceNow Administrators can see the field, but standard users or support teams cannot.
  4. Attempting to add an endpoint fails with the error: "Entered details are invalid [Please verify Host Url / Username / Password or Mid Server status]."

Environment

VCF Automation Plug-In for ServiceNow 8.x and later versions.

Cause

The user account lacks the required ServiceNow Role-Based Access Control (RBAC) permissions to view and interact with the necessary CMDB and plugin tables. Specifically, the missing cmdb_read role is a common cause for field visibility failures in this context.

Resolution

To resolve this issue, ensure the user account assigned to the VCF Plug-In has the appropriate roles mapped in ServiceNow.

  1. Navigate to the ServiceNow User Administration module.
  2. Search for the user account associated with the VCF Plug-In integration.
  3. Open the "Roles" related list.
  4. Add the following required roles:
    • cmdb_read
    • x_vmw_cloudservice.vra_end_user
    • x_vmw_cloudservice.vra_catalog_admin
  5. Save the record.
  6. Refresh the VCF Plug-In "Manage Endpoints" form to verify the MID server field is now visible.

Additional Information

Ensure that your ServiceNow instance has enabled the necessary ACLs for these roles. If the issue persists, verify that no conflicting UI Policies or Client Scripts are hiding the field for specific user roles.