Cloud Director with SAML

[anpa]

Hi,

Have anyone tried using Cloud Director integration with Veeam 11 where Cloud Director has SAML active for the Provider-tenant?
I've got some issues logging in, and it worked before we activated SAML.
Perhaps the user needs to be configured differently? (administrator@system instead of just administrator?)

/Andreas

[Dima P.]

Hello Andreas,

In case of single sign-on with SAML you should use Username@Suffix. Here is the detailed configuration guide to check your settings. Thanks!

[anpa]

Thanks Dima,

When reading my post again, I realized I missed some crucial details! My apologies!

I'm trying to add VCD as a resource in VBR Console, and use a local user for the Provider tenant (not any user tenant) - but the Provider tenant has SAML activated as well.
So basically I'm trying to add a resource that has both local users and SAML activated, hope that clarifies.

/Andreas

[anpa]

This turned out to be a very strange issue.

Not related to SAML. It never works via the load balancer, and sometimes it works against the cells without SAML. However, I cannot configure any jobs due to this error:

Failed to parse GUID from string [https://<hostname>.vmlabb.local/sdk]

Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).

Very strange, perhaps I need to open a support case for this.

[Andreas Neufert]

I guess you use vCD 11.1.2 and there is a known VMware bug where a VMware field contains an URL instead of a GUID.
vmware-vsphere-f24/vcloud-support-details-t69255.html

You can find the VMware bug number in there. I think VMware still does not have any solution to this other than asking customer to upgrade to later version.

[anpa]

Thanks!

Strange, we're on 6.7 U3 and VCD 10.2.2 in our lab (where we encountered this), so I guess the solution is to go for 7.0 U2 then? Darn it

Found the error for the GUID part (see in post you linked to), wonder if that explains the login issue as well (SAML still disabled, Veeam says invalid password).

/Andreas

[anpa]

All seems to be working now, even with SAML activated. I patched the vCenter (unrelated), and after the patch and vCD established connectivity, the UUID was properly updated in the table.