Are you performing a simple install(1 vRA appliance and 1 Windows IaaS)? Load balancer?
In my simple deployment with no load balancer for our Dev environment, I chose the settings below. IaaS Web Address should be the address used by clients to access. Notice that in my environment, this is a CNAME that references the A record for the IaaS server.
Also, when using a CNAME or alternate DNS record for the vRA appliance web address, the IDP will be affected. This problem doesn't manifest itself for users of vRA but will cause problems if you use the integrated vRO Instance. You will need to modify the following setting in the IDP to match the public DNS value for the vRA appliance. See the post and KB below:
Thanks rstoker13! Yes, I am using a simple install for testing purposes, no LBs yet (though I am going to be looking to LB this soon, so I am sure I'll have more questions then).
I see what I did wrong - when I deployed I put the FQDN of the .local name for the IaaS server for "IaaS Web Address" - naturally that won't work. I wish there was a little comment there like in the vRA field.
That said - is it too late to change? Also, how can I put a valid external cert on the IaaS server then? I had issues with it complaining that the SAN, blah blah.
I appreciate your response I would have never found the KB below, actually!
Edit: I changed the IdP hostname to match my FQDN config for vRA (cloud.domain.com) and no longer get kicked over to vra.domain.local
But how do I change the IaaS web address and do I even bother?