<?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: Retrieve report as file using HTTPWEBREQUEST in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303395#M5625</link>
    <description>&lt;P&gt;After adapting the Splunk SDK, we can send search outputs to an external server in an acceptable format. &lt;/P&gt;</description>
    <pubDate>Tue, 06 Nov 2018 21:47:16 GMT</pubDate>
    <dc:creator>dorgra</dc:creator>
    <dc:date>2018-11-06T21:47:16Z</dc:date>
    <item>
      <title>Retrieve report as file using HTTPWEBREQUEST</title>
      <link>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303393#M5623</link>
      <description>&lt;P&gt;I need to send over 300 emails out each day for a user's manager to attest to privileged activity. The report I retrieve is easily parsed and inserted into an SQL table. The user manager list changes. This list is retrievable from an HR feed and eliminates the need to maintain that ever changing list. &lt;/P&gt;

&lt;P&gt;I use VB.NET and the REST API. I can't use cURL.&lt;BR /&gt;
1. The company I work for will not permit scripting. Hence, I can't deliver the report to a server.&lt;BR /&gt;
2. The company will not permit retrieval from the Linux servers used for report storage. &lt;BR /&gt;
3. I need to ignore certificates. I believe I have this accomplished with System.Net.ServicePointManager.ServerCertificateValidationCallback&lt;BR /&gt;
4. I must pass the userid and password in the header.&lt;BR /&gt;
5. My current error message is "Unable to connect to the remote server"&lt;/P&gt;

&lt;P&gt;Anyone know where I can find some examples? &lt;/P&gt;</description>
      <pubDate>Fri, 24 Nov 2017 16:48:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303393#M5623</guid>
      <dc:creator>dorgra</dc:creator>
      <dc:date>2017-11-24T16:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: Retrieve report as file using HTTPWEBREQUEST</title>
      <link>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303394#M5624</link>
      <description>&lt;P&gt;The answer turned out to be an adaptation of the Splunk SDK. &lt;/P&gt;</description>
      <pubDate>Mon, 05 Nov 2018 14:32:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303394#M5624</guid>
      <dc:creator>dorgra</dc:creator>
      <dc:date>2018-11-05T14:32:01Z</dc:date>
    </item>
    <item>
      <title>Re: Retrieve report as file using HTTPWEBREQUEST</title>
      <link>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303395#M5625</link>
      <description>&lt;P&gt;After adapting the Splunk SDK, we can send search outputs to an external server in an acceptable format. &lt;/P&gt;</description>
      <pubDate>Tue, 06 Nov 2018 21:47:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/Retrieve-report-as-file-using-HTTPWEBREQUEST/m-p/303395#M5625</guid>
      <dc:creator>dorgra</dc:creator>
      <dc:date>2018-11-06T21:47:16Z</dc:date>
    </item>
  </channel>
</rss>

