<?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 SSL VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssl-vpn/m-p/1404186#M742693</link>
    <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have SSL VPN connectivity up and running on several ASA's, but I don't want my users to be able to login from anywhere or from any pc. I would essentially like to disable the clientless aspect of SSL VPN so that users can only login if that have the software preinstelled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently using a local CA truspoint, and I know I could get around this issue by only allowing users to connect who have a valid certificate already installed on their machine, but I'm looking for a quick easy win for the short term.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I remove the svc image statements from the config, or remove svc enable, the device refuses to authenticate me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 17:16:24 GMT</pubDate>
    <dc:creator>Gatling_uk</dc:creator>
    <dc:date>2019-03-11T17:16:24Z</dc:date>
    <item>
      <title>SSL VPN</title>
      <link>https://community.cisco.com/t5/network-security/ssl-vpn/m-p/1404186#M742693</link>
      <description>&lt;P&gt;Hello all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have SSL VPN connectivity up and running on several ASA's, but I don't want my users to be able to login from anywhere or from any pc. I would essentially like to disable the clientless aspect of SSL VPN so that users can only login if that have the software preinstelled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm currently using a local CA truspoint, and I know I could get around this issue by only allowing users to connect who have a valid certificate already installed on their machine, but I'm looking for a quick easy win for the short term.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I remove the svc image statements from the config, or remove svc enable, the device refuses to authenticate me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:16:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-vpn/m-p/1404186#M742693</guid>
      <dc:creator>Gatling_uk</dc:creator>
      <dc:date>2019-03-11T17:16:24Z</dc:date>
    </item>
    <item>
      <title>Re: SSL VPN</title>
      <link>https://community.cisco.com/t5/network-security/ssl-vpn/m-p/1404187#M742732</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have decided to change the port that it listens on as a temporary measure.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for looking anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Mar 2010 15:55:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssl-vpn/m-p/1404187#M742732</guid>
      <dc:creator>Gatling_uk</dc:creator>
      <dc:date>2010-03-02T15:55:54Z</dc:date>
    </item>
  </channel>
</rss>

