<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Kevin,<br>
<br>
Thank you for your help.<br>
<br>
I have configured jetty container for alternate HTTPS ports in
jetty's start.ini as follows:
<br>
<br>
jetty.port=9080<br>
jetty.secure.port=9443<br>
jetty.https.port=9443<br>
jetty.spdy.port=9443<br>
<pre wrap="">
</pre>
Yet the idp metadata that is available at:<br>
<br>
<a class="moz-txt-link-freetext" href="http://localhost:9080/idp/profile/Metadata/SAML">http://localhost:9080/idp/profile/Metadata/SAML</a><br>
<br>
uses port 8443 instead of 9443.<br>
<br>
Here is an example from the IdP metadata page:<br>
<br>
<AttributeService
Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding"
Location="<a class="moz-txt-link-freetext" href="https://wellfleet1.wellfleetsoftware.com">https://wellfleet1.wellfleetsoftware.com</a>:<b>8443</b>/idp/profile/SAML1/SOAP/AttributeQuery"/><br>
<br>
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?<br>
<br>
Thanks again for your help.<br>
<br>
On 05/21/2013 08:55 AM, Kevin P. Foote wrote:<br>
</div>
<blockquote cite="mid:alpine.LFD.2.03.1305210851030.17234@iup.edu"
type="cite">
<pre wrap="">
On Tue, 21 May 2013, Farrukh Najmi wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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).
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Farrukh Najmi
Web: <a class="moz-txt-link-freetext" href="http://www.wellfleetsoftware.com">http://www.wellfleetsoftware.com</a>
</pre>
</body>
</html>