Issue where SNI header is not being passed to the Aria Automation nodes.
search cancel

Issue where SNI header is not being passed to the Aria Automation nodes.

book

Article ID: 418021

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

    • When using REST based Workflows and/or Actions such "Add a Rest Host" fails where you are leveraging load balanced Kubernetes instances with Ingress Controllers set on the target server.
    • The Server Name Indicator (SNI) is not currently implement as part of the certificate passed to the target server from the vRO, hence leading a "Kubernetes Fake Certificate" being pulled instead of the Certificate Authority generated certificate as intended.

Environment

Aria Orchestrator 8.18.x

Cause

This issue occurs as the server expects the certificate with the SNI completed.

Resolution

Fix implemented and will be addressed in a future release.

Powered by Wolken Software