Aria Automation Ansible integration fails with SSH private key protected by a passphrase
search cancel

Aria Automation Ansible integration fails with SSH private key protected by a passphrase

book

Article ID: 422054

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

When configuring an Ansible Open Source integration in Aria Automation using an SSH private key for authentication, the connection fails after 3 retries. This occurs even when the private key has been validated to work outside of Aria Automation (e.g., via a direct SSH session).

The error indicates that the connection was rejected 3 times.

Environment

 

VMware Aria Automation (formerly vRealize Automation)

 

 

 

Cause

The Aria Automation Ansible Open Source integration is designed to support only unencrypted SSH private keys. The integration interface does not have a field or mechanism to store or pass a passphrase associated with an encrypted private key during the connection attempt.

Resolution

To successfully connect the Ansible integration, you must use an unencrypted SSH private key.

  1. Generate a new key pair without a passphrase.

    • Note: You may use tools like ssh-keygen or PuTTYgen to create a new key pair. Ensure you leave the passphrase field empty.

    • Alternatively you can just regenerate the private key from your existing public key.

  2. Verify the new private key is unencrypted. The key file should not contain the header "ENCRYPTED" (or similar) at the beginning of the file content.

  3. Update the Ansible target host with the new corresponding public key (if public key was regenerated during step 1.).

  4. In Aria Automation, navigate to the Ansible Open Source integration settings.

  5. Replace the contents of the private key field with the new, unencrypted private key.

  6. Save and test the connection.

Additional Information

This is expected behavior and a current limitation of the Ansible Open Source integration in Aria Automation. If you are unable to use an unencrypted key due to security policies, you would need to explore alternative integration methods (e.g., password-based authentication) or consider using a different integration method (if available).

Powered by Wolken Software