Veeam Self-Service Portal vCloud Director Plugin

[cdlansys]

Dear all,

Following the suggestion received from your technician under CASE #07989279, we are reaching out for further clarification and support regarding the vCloud Director Plugin integration with the Self-Service Portal.

As previously indicated:

“From what I was able to find out, the multiple URLs method is not supposed to work at all, so I don't think the logs are needed.
I think it might be best to report this as a Feature Request to our forums.”

However, given the impact on our production and DR environments, we would appreciate additional guidance before proceeding with a feature request.

Current Environment

Two vCloud Director instances:

Production site in Milan

Disaster Recovery site in Rome

The vCloud Director plugin is installed on both instances to allow tenants within the VDC to access the Self-Service Portal.

ISSUE DESCRIPTION:

We identified that the plugin cannot function simultaneously on both sites due to limitations within Enterprise Manager and the Self-Service Portal related to security headers.

Referring to the community discussion:
https://community.veeam.com/discussion- ... vider-4800

We attempted to configure the following parameter:

<add key="security-headers:vcdIpOrDnsAddress" value="https://*.our-domain.com/" />

Unfortunately, this configuration does not work.

At present, the only configuration that allows the plugin to operate correctly on both sites is:

<add key="security-headers:vcdIpOrDnsAddress" value="*" />

As already confirmed by your support team, this wildcard setting is not considered secure. However, it is currently the only functional option available to us.

REQUEST:

Could you please advise:

Is there a supported and secure method to allow multiple vCloud Director URLs?

Is there any alternative configuration that would allow both sites to function correctly without using the global wildcard (*)?

Is this a known limitation with a roadmap for improvement?

We have also tested additional approaches, including:

IIS custom headers

Multiple values separated by commas or spaces in the security header configuration

None of these methods were successful.


Many Thanks

Andrea

[cdlansys]

Hello Guys,

any news?

Thanks a lot