If you have ever configured SAML authentication for a load-balanced Horizon Connection Server cluster, you know the pain. For years, every Connection Server insisted on being a unique snowflake—each generating its own local SAML metadata, its own signing certificate, and its own distinct identity.
This architectural quirk made configuring