Added consistentAddress property to Session.
authorScott Cantor <cantor.2@osu.edu>
Thu, 5 Jan 2006 02:59:09 +0000 (02:59 +0000)
committerScott Cantor <cantor.2@osu.edu>
Thu, 5 Jan 2006 02:59:09 +0000 (02:59 +0000)
configs/shibboleth.xml.in
schemas/shibboleth-targetconfig-1.0.xsd

index 59c452d..9881932 100644 (file)
                will force the protocol to be https. You should also add a cookieProps setting of "; path=/; secure"
                in that case. Note that while we default checkAddress to "false", this has a negative
                impact on the security of the SP. Stealing cookies/sessions is much easier with this
-               disabled.
+               disabled. The consistentAddress property is even more critical, and should rarely be
+               disabled. It will only trip if a client uses a different source address at the SP
+               after the cookie is issued. Allowing that means many scripting attacks against
+               applications can result in theft and impersonation using the Shibboleth session.
                -->
-               <Sessions lifetime="7200" timeout="3600" checkAddress="false"
+               <Sessions lifetime="7200" timeout="3600" checkAddress="false" consistentAddress="true"
                        handlerURL="/Shibboleth.sso" handlerSSL="false" idpHistory="true" idpHistoryDays="7">
                        
                        <!--
index 3f2db64..e703d7a 100644 (file)
                        <attribute name="lifetime" type="unsignedInt" use="optional"/>
                        <attribute name="timeout" type="unsignedInt" use="optional"/>
                        <attribute name="checkAddress" type="boolean" use="optional"/>
+                       <attribute name="consistentAddress" type="boolean" use="optional" default="true"/>
                        <attribute name="checkReplay" type="boolean" use="optional" default="true"/>
                        <anyAttribute namespace="##other" processContents="lax"/>
                </complexType>