VM Tag assignment failure in Java-Based workflow due to authentication error com.vmware.vapi.std.errors.unauthenticated
search cancel

VM Tag assignment failure in Java-Based workflow due to authentication error com.vmware.vapi.std.errors.unauthenticated

book

Article ID: 392175

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • While attempting to run a Java-based workflow for VM tag assignment, the workflow failed with the following error message:

    com.vmware.vapi.std.errors.unauthenticated => {data=<unset>, error_type=UNAUTHENTICATED, messages=[com.vmware.vapi.std.localizable_message => {args=[], default_message=Authentication required., localized=<unset>, id=com.vmware.vapi.endpoint.method.authentication.required, params=<unset>}], challenge=Basic realm="VAPI endpoint",SIGN realm=<UUID of Endpoint>,service="VAPI endpoint",sts="https://<VCFQN>/sts/STSService/,<VC_Domain_Name>"} (Workflow:Tag_VM / Scriptable task (item1)#12)

  • The error indicates that authentication is required for the vAPI endpoint, and this prevents the workflow from tagging the VM.

Environment

Aria Automation 8.X

Cause

The error is caused by invalid credentials stored in the vAPI endpoint configuration within Aria Automation Orchestrator. This usually occurs when the password for the vAPI endpoint is incorrect or outdated, preventing authentication with the endpoint.

Resolution

To resolve the issue, follow these steps:

  1. Remove the existing vAPI endpoint:
    • Log into Aria Orchestrator.
    • Navigate to Library > Workflows.
    • Expand Library, then expand vAPI.
    • Run the Remove vAPI endpoint workflow.
    • Provide the necessary details to remove the existing vAPI endpoint.
  2. Re-add the vAPI endpoint with correct credentials:
    • Once the vAPI endpoint is removed, run the Add vAPI endpoint workflow to add the endpoint back with the correct credentials.
    • Ensure that the username and password for the vAPI endpoint are entered correctly.
  3. Test the workflow:
    • After adding the endpoint with the correct credentials, run the VM tag assignment workflow again to verify that the error is resolved.