After upgrading standalone Orchestrator 9.0 authentication provider is not configured
search cancel

After upgrading standalone Orchestrator 9.0 authentication provider is not configured

book

Article ID: 407495

calendar_today

Updated On:

Products

VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

  • After upgrading standalone Aria Automation Orchestrator 8.18.x to VCF Operations Orchestrator 9.0, the UI at https://<your_orchestrator_FQDN>/orchestration-ui/ may be inaccessible

  • Running vracli vro authentication returns "No authentication provider configured."

Environment

Standalone VCF Operations Orchestrator 9.0. 

Cause

Known issue in Standalone VCF Operations Orchestrator 9.0. The provided password is not assigned to the correct variable during upgrade.

Resolution

This issue has been resolved in VCF Orchestrator 9.0.1.

To work around the issue, provide the password in environment variable then upgrade.

  1. Connect to the Orchestrator appliance via SSH or console as root
        Note: In a cluster, the commands only need to be run on one node
  2. Provide the password as an environmental variable by running
        export VRO_SSO_PASSWORD=<the password>
  3. In the same terminal start the upgrade as per the documentation: Configuring the Automation Orchestrator Appliance authentication provider with the command line interface

Additional Information

For other known issues, related to upgrading, please refer to VCF Operations Orchestrator 9 Known Issues