In my lab environment, I have deployed an Embedded VCSA 6.5 (this also works with an External PSC) and vRealize Automation 7.2 (this was prior to 7.3 getting released but should work as well).
If this is something that you are interested in or would like to see specific External IDP setup/configuration, feel free to leave a comment. I know this is something the PSC team is currently looking into for External IDP support. I know there are number of customers who would also like to see the reverse of this configuration, where PSC can use vIDM as an External IDP. I also learned that we had officially supported this since vRA 7.0 which was great to hear as well. In reading some of our internal Wikis and working with one of the vIDM Engineers, since I was stuck on a particular step, I was able to finally get this to work which I have outlined the steps below.
Since both solutions spoke SAML, it was merely figuring out process on setting up the External IDP using the PSC. vIDM already supports a large number of websso applications as seen here and it itself can also be used as an External IDP to integrate with things like Active Directory Federation Services (ADFS) for example.įor some customers who are more familiar with the PSC, this is a convenient way to unify their authentication between the different vRealize products which support vIDM and integrating that directly with PSC. I was doing some research on an inquiry that I had received from a customer who was interested in configuring their vRealize Automation (vRA) instance to use vCenter's Platform Services Controller (PSC) as an External Identity Provider (IDP) rather than the default VMware Identity Manager (vIDM) which vRA supports natively out of the box.
0 kommentar(er)
