<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ACE - keep user on SSL only if logged in in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/ace-keep-user-on-ssl-only-if-logged-in/m-p/1324109#M27482</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ACE has no knowledge about what happened in a previous connection.&lt;/P&gt;&lt;P&gt;All you can do is inspect the header of the new http request and identify some information which could identify if the user is logged in or not.&lt;/P&gt;&lt;P&gt;For example, if the server sets a particular cookie when the client is logged in, you can check the presence of this cookie to determine if the client is connected and send the redirect to https.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT, since the client will potentially keep the same cookie, even if he logs out, then ace will continue redirecting the client to https.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only the server has the complete knowledge of the client state.&lt;/P&gt;&lt;P&gt;So the redirect should come from the server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 30 Jul 2009 12:19:30 GMT</pubDate>
    <dc:creator>Gilles Dufour</dc:creator>
    <dc:date>2009-07-30T12:19:30Z</dc:date>
    <item>
      <title>ACE - keep user on SSL only if logged in</title>
      <link>https://community.cisco.com/t5/application-networking/ace-keep-user-on-ssl-only-if-logged-in/m-p/1324108#M27481</link>
      <description>&lt;P&gt;Hi everyone&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a complicated scenario which we need to achieve using the ACE4710. This is what we want to achieve:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) User browses to site &lt;A class="jive-link-custom" href="http://www.site.com" target="_blank"&gt;http://www.site.com&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) User logs in and login is posted to secure path &lt;A class="jive-link-custom" href="https://www.site.com/myaccount." target="_blank"&gt;https://www.site.com/myaccount.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3) Once the user is logged in, all subsequent requests to &lt;A class="jive-link-custom" href="http://www.site.com/" target="_blank"&gt;http://www.site.com/&lt;/A&gt;* need to be redirected to &lt;A class="jive-link-custom" href="https://www.site.com/" target="_blank"&gt;https://www.site.com/&lt;/A&gt;*. In other words, once the user has accessed /myaccount within the session, all further requests must be SSL, no matter which page on the site they are on.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this possible with the ACE?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jul 2009 05:12:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-keep-user-on-ssl-only-if-logged-in/m-p/1324108#M27481</guid>
      <dc:creator>osiristrading</dc:creator>
      <dc:date>2009-07-30T05:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: ACE - keep user on SSL only if logged in</title>
      <link>https://community.cisco.com/t5/application-networking/ace-keep-user-on-ssl-only-if-logged-in/m-p/1324109#M27482</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ACE has no knowledge about what happened in a previous connection.&lt;/P&gt;&lt;P&gt;All you can do is inspect the header of the new http request and identify some information which could identify if the user is logged in or not.&lt;/P&gt;&lt;P&gt;For example, if the server sets a particular cookie when the client is logged in, you can check the presence of this cookie to determine if the client is connected and send the redirect to https.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT, since the client will potentially keep the same cookie, even if he logs out, then ace will continue redirecting the client to https.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Only the server has the complete knowledge of the client state.&lt;/P&gt;&lt;P&gt;So the redirect should come from the server. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 30 Jul 2009 12:19:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/ace-keep-user-on-ssl-only-if-logged-in/m-p/1324109#M27482</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2009-07-30T12:19:30Z</dc:date>
    </item>
  </channel>
</rss>

