<?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: Splunk through Cisco ASA Clientless WebVPN (Bug?) in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77517#M4185</link>
    <description>&lt;P&gt;If your IT team will support/allow it, the Cisco WebVPN should be able to use the "Anyconnect" client to give you "true" connectivity through the WebVPN, which would be an acceptable workaround for this.&lt;/P&gt;</description>
    <pubDate>Mon, 19 Sep 2011 15:18:07 GMT</pubDate>
    <dc:creator>dwaddle</dc:creator>
    <dc:date>2011-09-19T15:18:07Z</dc:date>
    <item>
      <title>Splunk through Cisco ASA Clientless WebVPN (Bug?)</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77515#M4183</link>
      <description>&lt;P&gt;When using Splunk through Cisco ASA Clientless WebVPN, none of the dropdown menus work.&lt;/P&gt;

&lt;P&gt;Am i doing something wrong, is it a bug, or is it just the way the dropdown menus work that cannot be used through a proxy system like WebVPN ?&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 07:25:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77515#M4183</guid>
      <dc:creator>ultima</dc:creator>
      <dc:date>2011-09-19T07:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk through Cisco ASA Clientless WebVPN (Bug?)</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77516#M4184</link>
      <description>&lt;P&gt;This kind of "VPN", which relies on rewriting URLs as they go in and out, are inherently very limited with any web application that uses browser-side script, especially if that script performs call-backs. (This includes just about web application with a modern UI. Flash is even less likely to work.) I am surprised that the only thing you have seen is the dropdowns failing. &lt;/P&gt;

&lt;P&gt;This is not a Splunk bug, but a limitation of the type of gateway you are using.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 14:47:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77516#M4184</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-09-19T14:47:12Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk through Cisco ASA Clientless WebVPN (Bug?)</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77517#M4185</link>
      <description>&lt;P&gt;If your IT team will support/allow it, the Cisco WebVPN should be able to use the "Anyconnect" client to give you "true" connectivity through the WebVPN, which would be an acceptable workaround for this.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 15:18:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/Splunk-through-Cisco-ASA-Clientless-WebVPN-Bug/m-p/77517#M4185</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2011-09-19T15:18:07Z</dc:date>
    </item>
  </channel>
</rss>

