<?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: Can eventtypes for specific users be disabled via the REST API? in Security</title>
    <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205158#M5901</link>
    <description>&lt;P&gt;Thanks for the answer somesoni2,  however that doesn't appear to work.  The API call succeeds, but it still creates a duplicate eventtype.  The duplicate is owned by the user provided in the URL at  instead of the API user like before, but it's still not updating the existing eventtype.&lt;/P&gt;</description>
    <pubDate>Thu, 22 Sep 2016 16:07:55 GMT</pubDate>
    <dc:creator>jllewellyn4847</dc:creator>
    <dc:date>2016-09-22T16:07:55Z</dc:date>
    <item>
      <title>Can eventtypes for specific users be disabled via the REST API?</title>
      <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205156#M5899</link>
      <description>&lt;P&gt;I'd like to disable eventtypes via the REST API.  These eventtypes could be owned by a variety of users, but I want to make my API calls with a single user.  According to the Splunk API docs, the correct way to do this is to POST to /services/saved/eventtypes/ with disabled=1.  This works fine when making the API call as the user that owns the event type, however, if I make the same call as a different user, it creates a disabled duplicate eventtype with the same name, owned by the user that made the API call.  The original eventtype remains enabled.&lt;/P&gt;

&lt;P&gt;So, when updating/disabling an eventtype via the API, is there any way to specify the owner of that eventtype in the POST?  Or is there a way to ensure that the API call will operate on the existing eventtype regardless of the owner, instead of creating a new eventtype?&lt;/P&gt;</description>
      <pubDate>Wed, 21 Sep 2016 16:28:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205156#M5899</guid>
      <dc:creator>jllewellyn4847</dc:creator>
      <dc:date>2016-09-21T16:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Can eventtypes for specific users be disabled via the REST API?</title>
      <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205157#M5900</link>
      <description>&lt;P&gt;Try this REST API endpoint for updating user specific event types (example with curl)&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -k -u admin:pass &lt;A href="https://yoursplunkserver:mgmtport/servicesNS/usernameHere/appnameHere/saved/eventtypes/eventtypenameHere" target="test_blank"&gt;https://yoursplunkserver:mgmtport/servicesNS/usernameHere/appnameHere/saved/eventtypes/eventtypenameHere&lt;/A&gt; -d disabled=1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Update the admin, pass, yoursplunkserver, mgmtport, usernameHere, appnameHere and eventtypenameHere per your environment.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Update&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;Try this. Seems to be working for me.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;curl -X POST -k -u admin:pass &lt;A href="https://yoursplunkserver:mgmtport/servicesNS/nobody/appnameHere/saved/eventtypes/eventtypenameHere/disable" target="test_blank"&gt;https://yoursplunkserver:mgmtport/servicesNS/nobody/appnameHere/saved/eventtypes/eventtypenameHere/disable&lt;/A&gt;
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 21 Sep 2016 21:26:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205157#M5900</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-09-21T21:26:26Z</dc:date>
    </item>
    <item>
      <title>Re: Can eventtypes for specific users be disabled via the REST API?</title>
      <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205158#M5901</link>
      <description>&lt;P&gt;Thanks for the answer somesoni2,  however that doesn't appear to work.  The API call succeeds, but it still creates a duplicate eventtype.  The duplicate is owned by the user provided in the URL at  instead of the API user like before, but it's still not updating the existing eventtype.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 16:07:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205158#M5901</guid>
      <dc:creator>jllewellyn4847</dc:creator>
      <dc:date>2016-09-22T16:07:55Z</dc:date>
    </item>
    <item>
      <title>Re: Can eventtypes for specific users be disabled via the REST API?</title>
      <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205159#M5902</link>
      <description>&lt;P&gt;Give the updated answer a try.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 16:35:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205159#M5902</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2016-09-22T16:35:23Z</dc:date>
    </item>
    <item>
      <title>Re: Can eventtypes for specific users be disabled via the REST API?</title>
      <link>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205160#M5903</link>
      <description>&lt;P&gt;That works for me.  Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 22 Sep 2016 21:44:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Can-eventtypes-for-specific-users-be-disabled-via-the-REST-API/m-p/205160#M5903</guid>
      <dc:creator>jllewellyn4847</dc:creator>
      <dc:date>2016-09-22T21:44:00Z</dc:date>
    </item>
  </channel>
</rss>

