[sso] login url misses custom port on self-hosted deployment

[SomaticIT]

Steps To Reproduce

1. Configure a self-hosted deployment with a custom URl containing a custom port (eg: https://bitwarden.myserver.com:8443)
2. Create a SSO configuration with Azure SAML (I think it's the same with another provider)
3. Try connect using SSO

Expected Result

You should be redirected to:
https://bitwarden.myserver.com:8443/identity/sso/Login?...

Actual Result

You are redirected to:
https://bitwarden.myserver.com/identity/sso/Login?...
Notice the missing port

Screenshots or Videos

No response

Additional Context

No response

Build Version

2024.10.2

Environment

Self-Hosted

Environment Details

• Operating System: Debian 6.1.85-1
• Environment: Docker 24.0.5
• Hardware: AMD EPYC 7281 (3 dedicated cores) / 4GB RAM

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[Neonwarden]

Hi there,

We use GitHub issues as a place to track bugs and other development-related issues. Please write us back using our “Contact support” form located on our Help Center (https://bitwarden.com/help/).

You can include a link to this issue in the message content.

Alternatively, you can also search for an answer in our help documentation or get help from other Bitwarden users on our community forums (https://community.bitwarden.com/c/support/).

The issue here will be closed.

Thanks!

[SomaticIT]

@Neonwarden, I'm not sure I understand your message. This a bug and so, a development-related issue.
That's why I think this is the good place to talk about this.
Doesn't it?