SAML message delivered with POST to incorrect server URL. with Google Cloud Load Balancer

O'Quinn, Dennis DENNIS_OQUINN at homedepot.com
Thu May 31 20:52:15 EDT 2018


Hi, I am very new to Shibboleth and am attempting to configure it to work with Ping Identity as the IdP and Shibboleth as the SP inside of Google Cloud Platform (GCP) behind a GCP LB.  Running Shibboleth 2 on Linux and Apache 2.4

The will be used to authenticate users for access to SAS which is configured as HTTPS and listening on Port 8343.  The LB is listening on Port 443 and will pass data through while changing the target port to 8343 in order to reach the SAS web server.

When we generate the SP metadata all URLS come out as https://<saswebserver>:8343/<https://%3csaswebserver%3e:8343/>....

If we use that metadata unchanged then the return posts from the IdP will be stopped at the LB since it is not listening on 8343.

If we change the metadata to remove 8343 or change it to 443, then we can get through the LB, but, we get the following error...

ERROR OpenSAML.MessageDecoder.SAML2POST [1]: POST targeted at (https://sascloud.com:443/Shibboleth.sso/SAML2/POST), but delivered to (https://sascloud.com:8343/Shibboleth.sso/SAML2/POST)

Note: the name of the GCP VM internal host name (i.e., the SAS Web server) is completely different from sascloud.com.  sascloud.com is simply our external/public DNS name for the LB.  The url is changed from https://sascloud.com:443/... to https://<sashostname>:8343/<https://%3csashostname%3e:8343/>....  by the LB backend as it is passed into GCP.

Is the httpd.conf ServerName directive the only way to control this behavior and get the target and destination names to match?  Or is there a directive (or directives) that can be specified in Shibboleth2.xml that can perform the translation and allow the authentication to work and allow the user to get to their SAS GUI?

Thanks in advance for any guidance, Dennis

________________________________

The information in this Internet Email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this Email by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this Email are subject to the terms and conditions expressed in any applicable governing The Home Depot terms of business or client engagement letter. The Home Depot disclaims all responsibility and liability for the accuracy and content of this attachment and for any damages or losses arising from any inaccuracies, errors, viruses, e.g., worms, trojan horses, etc., or other items of a destructive nature, which may be contained in this attachment and shall not be liable for direct, indirect, consequential or special damages in connection with this e-mail message or its attachment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20180601/d8a4e75f/attachment.html>


More information about the users mailing list