CA Release Automation offers the ability to configure an action/flow/process to run as a specific alternate user. This feature is commonly referred to as user impersonation. By default, the CA Release Automation agent will use a java implementation of ssh to connect to the localhost using <specifiedUser>@127.0.0.1. This method does not require any additional agent machine configurations (beside the ability to ssh into the machine as the user you want to use). Other methods (such as sudo or su) do require specific agent machine configurations and are described in more detail here: https://docops.ca.com/ca-release-automation/6-1/en/installation/deploy-agents#DeployAgents-RunProcessesUnderDifferentUsers–Unix/Linux
When configuring an agent to allow for running process under different users (user impersonation) via SSH authentication, is it possible to also configure it to use a key exchange?
Release Automation does not officially support using public/private keys for user impersonation via SSH authentication at this time. A custom workaround may be possible, in which case, please contact CA Services or discuss with us via the Release Automation Communities site for more information.
For more information regarding user impersonation, please refer to our Release Automation product documentation at https://docops.ca.com.
Was this information helpful?