Hi,
We have been experiencing inconsistent behavior with vRealize Automation 7.5 Authentication provider configuration which, when we do get configured, leads to even more inconsistent workflow execution. I now have 4 vRealize Automation environments configured in an attempt to determine the cause of our issues. As per my previous post a deployment of the vRA 7.5 Appliance and specifically the configuration of an Authentication Provider in vCO control center is a hit or miss affair for reasons I have not been able to identify. When I do manage to get a domain authentication source and admin group configured several workflows which we use in our vRA environment fail at the very first scriptable task with a java.lang.NullPointerException. When changing the Authentication source back to the default tenant (vsphere.local) with the admin group vsphere.local\vcoadmins my issues with workflows are gone and the workflows I am using proceed and function as expected.
In the vRO logs am event showing the following is logged...
VRAAuthorizationQueryService Failed while finding roles for principalId: "{Name: service-vra, domain: corp.local}", tenant" "corp". Granting an Operator role.
Suffice to say the Directory for our tenant corp was added without issues in vRA and the connector is joined to the domain. This issue is now occurring in all 4 environments I have deployed to isolate the issue and occur whether we are using a full enterprise deployment of 3 vRA nodes and 8 Windows VMs or a single vRA node and single IaaS VM.
I am unsure what I can next try to get a domain authentication source configured in vRO. Keeping the source as local is less than ideal and not in line with the VMware Validated Design architecture for 4.3.
Cheers