Requesting a Deployment for another user in VMware Aria Automation 8.x

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In vRealize Automation 7.x, users could request a deployment on behalf of another user using the onBehalfOf parameter. However, in VMware Aria Automation 8.x, this functionality was deprecated. Customers looking to assign deployments to another user at request time are encountering challenges due to this change.

This article explains the current behavior in Aria Automation 8.x and provides a workaround to achieve similar functionality using Change Owner Day 2 actions.

Environment

VMware Aria Automation 8.3 - 8.18.1

Cause

• onBehalfOf functionality was removed in Aria Automation 8.x.
• Change Owner is now the intended replacement.
• Ownership can only be modified after a deployment has been successfully created.
• There is no built-in API to assign another user at the time of request.

Resolution

While Aria Automation 8.x does not allow requesting a deployment for another user at request time, the functionality can be simulated using a Change Owner Day 2 action after the deployment is complete.

Workaround:

1. Request the deployment normally.
2. Once the deployment is complete, manually execute the "Change Owner" Day 2 action:
   • Navigate to Deployments > Select Deployment > Actions > Change Owner
   • Assign the new owner from the list of eligible users.
3. Alternatively, automate the Change Owner action via API:
   • Capture the intended user during deployment request (e.g., via custom forms).
   • Store this value in a custom property.
   • Trigger the Change Owner Day 2 action using an API call post-deployment.

Note:

• Customers using DUO or other MFA solutions may need to extract an API bearer token via browser headers to authenticate API requests if the instructions located in Generate an Access Token and Bearer Token in VMware Aria Automation for API Authentication fails.