Configure IdP for alternate HTTP and HTTPS ports

[Farrukh Najmi]

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/7c9dc252/attachment.html