3550421 - SAML2 metadata is generated with incorrect hostname

1. A Service Provider (SP) configuration has been set up. Upon generating the SAML metadata file, it was observed that the parameters, such as the following examples, contain the server hostname instead of the web dispatcher/proxy hostname:

</m:KeyDescriptor>
<m:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://<serverHostname>/sap/saml2/sp/slo/"/>
<m:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://<serverHostname>/sap/saml2/sp/slo/"/>
<m:AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://<serverHostname>/sap/saml2/sp/acs/" index="0" isDefault="true"/>

2. A SAML trace collected during the metadata export reveals that the header "host: " contains the incorrect (server) hostname:

Incoming HTTP request:
---------------------------------------------

GET /sap/saml2/sp/metadata?sap-client=<clientNumber> HTTP/1.1

HTTP headers:
---------------------------------------------
 ~request_line:  GET /sap/saml2/sp/metadata?sap-client=<clientNumber> HTTP/1.1
 ~request_method:  GET
 ~request_uri:  /sap/saml2/sp/metadata?sap-client=<clientNumber>
 ~path:  /sap/saml2/sp/metadata
 ~path_translated:  /sap/saml2/sp/metadata
 ~query_string:  sap-client=<clientNumber>
 ~server_protocol:  HTTP/1.1
 host:  <serverHostname>

SAML, SAML2, metadata, hostname, URL, proxy , KBA , BC-SEC-LGN-SML , SAML 2.0 for ABAP , Problem