Configure IdP for alternate HTTP and HTTPS ports

[Paul Hethmon]

The IdP metadata file is generated from a template during the initial installation step. After that step, you will need to edit that file ($SHIB_HOME/metadata/idp-metadata.xml) to reflect any changes (like port numbers) that you have made.

Paul


From: Farrukh Najmi <farrukh at wellfleetsoftware.com<mailto:farrukh at wellfleetsoftware.com>>
Reply-To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Date: Tuesday, May 21, 2013 10:16 AM
To: Shibboleth Users <users at shibboleth.net<mailto:users at shibboleth.net>>
Subject: Re: Configure IdP for alternate HTTP and HTTPS ports


Just to be clear, the IdP may well be using port 9443 as configured in jetty but what it is advertising in its metadata descriptor at http://localhost:9080/idp/profile/Metadata/SAML is indicating that it is using port 8443. Thus any attempt by SP to communicate with its endpoints will fail due to the wrong port.

Also, it seems like it would be a good thing to include port information on the detailed status page at:

http://<host>:<port>/idp/status


On 05/21/2013 10:01 AM, Farrukh Najmi wrote:
Hi Kevin,

Thank you for your help.

I have configured jetty container for alternate HTTPS ports in  jetty's start.ini as follows:

jetty.port=9080
jetty.secure.port=9443
jetty.https.port=9443
jetty.spdy.port=9443
Yet the idp metadata that is available at:

http://localhost:9080/idp/profile/Metadata/SAML

uses port 8443 instead of 9443.

Here is an example from the IdP metadata page:

<AttributeService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding" Location="https://wellfleet1.wellfleetsoftware.com:8443/idp/profile/SAML1/SOAP/AttributeQuery"/>

Why is it using 8443 instead of 9443 (as configured in jetty's start.ini) and what am I doing wrong that is causing this to happen?

Thanks again for your help.

On 05/21/2013 08:55 AM, Kevin P. Foote wrote:

On Tue, 21 May 2013, Farrukh Najmi wrote:



Where can I find info on how to configure the IdP to use alternate ports
for HTTP and HTTPS endpoints (e.g. 9080 for HTTP and 9443 for HTTPS).


Port handling is a function of your container (jetty, tomcat, apache
etc.) not the IdP software...

The IdP endpoints are "configured" if you will and known by what is
published in your metadata for your IdP.





--
Regards,
Farrukh Najmi

Web: http://www.wellfleetsoftware.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20130521/f28bc9f3/attachment-0001.html