Hi all,
Great feedback—thank you for sharing your experiences!
Let me address some of the points mentioned above:
- Host Management (:10443) is a completely isolated component, running alongside other Veeam services present on the machine. Currently, it does not support SAML authentication, nor does it share the configuration set in Veeam Backup & Replication settings. This is definitely a possibility for future enhancement.
- The Service Provider (SP) Certificate is required to validate connections from the backup server to the identity provider. Selecting the Veeam backup server certificate should be sufficient to establish trust, and we could likely simplify the user experience here by selecting it by default for you.
- Certificate validation is considered a general best practice today, and I strongly suggest considering it for the future. It is a mandatory option when configuring in the settings, however it can be ignored by the identity provider.
- The certificate option "AuthnRequestsSigned" is currently under investigation; it may have an incorrect value set. Thank you for pointing this out!
- Certificate [and only it] change UX — this is definitely an area for improvement, and we already have it on track.
- Certificate management is also a tracked feature request that we are paying close attention to.
Hope that clears things up, and please keep the feedback coming!
Great feedback—thank you for sharing your experiences!
Let me address some of the points mentioned above:
- Host Management (:10443) is a completely isolated component, running alongside other Veeam services present on the machine. Currently, it does not support SAML authentication, nor does it share the configuration set in Veeam Backup & Replication settings. This is definitely a possibility for future enhancement.
- The Service Provider (SP) Certificate is required to validate connections from the backup server to the identity provider. Selecting the Veeam backup server certificate should be sufficient to establish trust, and we could likely simplify the user experience here by selecting it by default for you.
- Certificate validation is considered a general best practice today, and I strongly suggest considering it for the future. It is a mandatory option when configuring in the settings, however it can be ignored by the identity provider.
- The certificate option "AuthnRequestsSigned" is currently under investigation; it may have an incorrect value set. Thank you for pointing this out!
- Certificate [and only it] change UX — this is definitely an area for improvement, and we already have it on track.
- Certificate management is also a tracked feature request that we are paying close attention to.
Hope that clears things up, and please keep the feedback coming!
Statistics: Posted by Egor Yakovlev — Sep 29, 2025 4:29 pm







