Why shibboleth IdP idp-metadata.xml recommends 8443 for SOAP? -
after install.sh of 2.4.0 shibboleth identity server, idp-metadata.xml file created. why that? not enough secure use standard https/443 port?
<artifactresolutionservice binding="urn:oasis:names:tc:saml:1.0:bindings:soap-binding" location="https://idp.example.com:8443/idp/profile/saml1/soap/artifactresolution" index="1"/> <artifactresolutionservice binding="urn:oasis:names:tc:saml:2.0:bindings:soap" location="https://idp.example.com:8443/idp/profile/saml2/soap/artifactresolution" index="2"/> <singlelogoutservice binding="urn:oasis:names:tc:saml:2.0:bindings:soap" location="https://idp.example.com:8443/idp/profile/saml2/soap/slo" /> <attributeservice binding="urn:oasis:names:tc:saml:1.0:bindings:soap-binding" location="https://idp.example.com:8443/idp/profile/saml1/soap/attributequery"/> <attributeservice binding="urn:oasis:names:tc:saml:2.0:bindings:soap" location="https://idp.example.com:8443/idp/profile/saml2/soap/attributequery"/>
thanks,
tamas
using linux, non-privileged user "tomcat" cannot bind ports below 1024. front-end load-balancers apache , nginx start user root bind privileged ports port 80 , port 443. common setup involve running tomcat instance on unprivileged port 8080 or 8443 , proxying port via apache or nginx.
Comments
Post a Comment