Tested vCD 10 and found it the new login breaks all SAML Federations (System and Org). Finally got a confirmation today from VMware support that it’s indeed a known issue internally. This has not yet been updated to the vCD 10 release notes, but according to the information provided to me, this will be resolved in version 10.0.1.
In my testing scenario, i get the following error when accessing login page of an organization that has SAML enabled;
AssertionConsumerServiceIndex cannot be set when ProtocolBinding or AssertionConsumerServiceUrl are set.
The only known workaround to me is to use federation services login page to generate the token that is passed to vCD.
To see the full content, share this page by clicking one of the buttons below