Veeam ONE SAML Identity Provider Setup Fails When the Web Client Uses Port 443

KB ID: 4943
Product: Veeam ONE | 13.1
Last Modified: 2026-11-19
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When the Veeam ONE Web Client uses port 443, the SP entity ID URL and Assertion consumer URL fields in the Add Identity Provider wizard contain a colon with no port number. For example, the SP entity ID URL field shows:

https://<FQDN>:/api/Saml2/<Client ID>

The identity provider (IdP) rejects these values. For example, Microsoft Entra ID rejects the identifier with the error InvalidValue and the reply URL with the error Request_BadRequest.

Cause

This issue occurs because Veeam ONE 13.1 generates the SP entity ID URL and Assertion consumer URL from the Web Client port, and the port is empty when the Web Client uses port 443, the default HTTPS port. The generated URLs then contain a colon with no port number, which the IdP does not accept. The result is the same whether or not :443 is included in the address used to open the Web Client.

Note: This behavior will be changed in an upcoming Veeam ONE release.

Solution

  1. Change the Veeam ONE Web Client port to a port other than 443, for example the default port 1239. For the procedure, see KB2466: How to Change Veeam ONE Web Client Port. After the port change, restart the Veeam ONE Reporting Service. Until the service restarts, the wizard keeps generating the URLs with the old port. Update user bookmarks and firewall rules for the new port.
  2. Open the Veeam ONE Web Client using the FQDN that users will use, because the host in the generated URLs comes from the address in the browser. In the Add Identity Provider wizard, make sure that the SP entity ID URL and Assertion consumer URL contain the port number, for example https://<FQDN>:1239/api/Saml2/<Client ID>, and use these URLs to configure the IdP.

If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.

To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.