Login to Aria Orchestrator fails after authentication provider certificate is expired/replaced.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

Logging in to Aria Orchestrator fails as well as configuration validation from control center fails with error:

Expected state NEW or CERTIFICATE_NOT_ACCEPTED. State changed to NEW from APPROVED

Environment

Aria Orchestrator 8.17 and below Version

Cause

Certificate changes on the Authentication provider will affect the login resulting validation failure with error: Expected state NEW or CERTIFICATE_NOT_ACCEPTED.

Resolution

1. Login to Aria Orchestrator control center using root credentials.
2. On the Configure Authentication Provider page, click the UNREGISTER button next to the host address text box to unregister the authentication provider that is in use.
3. Re-register the authentication provider as configured previously.
   a) For Authentication provider via Aria Automation follow document:
          https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-automation/8-17/vco-installing-and-configuring-8-17/initial-configuration/configuring-a-standalone-orchestrator-server/configure-a-standalone-orchestrator-server-with-vrealize-automation-authentication.html
   b) For  Authentication provider via vSphere Authentication follow document:
          https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-automation/8-17/vco-installing-and-configuring-8-17/initial-configuration/configuring-a-standalone-orchestrator-server/configure-a-standalone-orchestrator-server-with-vsphere-authentication.html#GUID-61267B72-2963-4E22-9630-DA90AF40EC05-en