Sure this has been discussed before but will ask again 🙂
Just curious as to why you should not use the vRealize Automation authentication mode?
Any known downsides, etc?
Can provide more background if required.
Appreciate any thoughts! 🙂
Well it's pretty simple, if you're using vRO to provide services to vRA, use vRA-based authentication. If you don't have vRA at all, use vSphere authentication. vRA works with far more than just vSphere, so this provides an auth mechanism for vRO in environments where customers may not be doing any vSphere deployments at all.
vRealize Automation authentication mode will integrate with the embedded vIDM in vRA. Do you know which authentication provider you will be using for the ID source, Active Directory?
Thanks for the replies.
One of the reasons for the query is we currently use vRA-based authentication but need to deploy existing workflows to 3rd Party 7.1 vRa/VRo setup that is setup to use authentication. As part of testing we noticed some problems with the workflows as the 3rd Party setup means the vRA host is not part of the vRO component registry.
An example is the following did not work -
var VCACHost = vCACCAFEHostManager.getDefaultHostForTenant(tenant , true);
Anyway, on our side can get around this so was just curious why the 3rd party went with vSphere authentication and have sent them a query.
I think I just assumed vRA based authentication was the definite way to go.