<?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: set up an account for splunk developer in Security</title>
    <link>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111483#M3553</link>
    <description>&lt;P&gt;So as I'm sure you've found, a Splunk Admin can change Ownership of objects through the REST API as detailed in &lt;A href="http://answers.splunk.com/answers/115781/change-the-owner-of-a-saved-search-via-rest.html"&gt;this answer&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So simple options include either be part of the off boarding process and transfer ownership of Splunk objects to another employee. OR have a process by which Splunk objects are "promoted" to be owned by a generic user that no one has to log in as.&lt;/P&gt;

&lt;P&gt;At my company I'm pushing to moving to the idea that developers can work within test apps / environments all they want, but to go to production, they need to package custom Splunk App(s) which are managed in source control, peer-reviewed, and installed in appropriate environments by our configuration management solution (Chef). But that's going to take a while to get there &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jul 2015 13:30:03 GMT</pubDate>
    <dc:creator>acharlieh</dc:creator>
    <dc:date>2015-07-09T13:30:03Z</dc:date>
    <item>
      <title>set up an account for splunk developer</title>
      <link>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111482#M3552</link>
      <description>&lt;P&gt;In our Splunk infra, we have so many developers creating objects. We had just faced a problem when few number of employee left organization and their alerts stopped working as the owner(employee) id was disabled from active directory. Also objects were created using own id's.&lt;BR /&gt;
We thought of creating a group contains all the developers and share the password with all. So that none of the object will be disabled after user/developer leave company. We did not find it optimal from security point of view. Can anyone suggest for this issue? &lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 13:16:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111482#M3552</guid>
      <dc:creator>rajul_jain</dc:creator>
      <dc:date>2015-07-09T13:16:50Z</dc:date>
    </item>
    <item>
      <title>Re: set up an account for splunk developer</title>
      <link>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111483#M3553</link>
      <description>&lt;P&gt;So as I'm sure you've found, a Splunk Admin can change Ownership of objects through the REST API as detailed in &lt;A href="http://answers.splunk.com/answers/115781/change-the-owner-of-a-saved-search-via-rest.html"&gt;this answer&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;So simple options include either be part of the off boarding process and transfer ownership of Splunk objects to another employee. OR have a process by which Splunk objects are "promoted" to be owned by a generic user that no one has to log in as.&lt;/P&gt;

&lt;P&gt;At my company I'm pushing to moving to the idea that developers can work within test apps / environments all they want, but to go to production, they need to package custom Splunk App(s) which are managed in source control, peer-reviewed, and installed in appropriate environments by our configuration management solution (Chef). But that's going to take a while to get there &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jul 2015 13:30:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111483#M3553</guid>
      <dc:creator>acharlieh</dc:creator>
      <dc:date>2015-07-09T13:30:03Z</dc:date>
    </item>
    <item>
      <title>Re: set up an account for splunk developer</title>
      <link>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111484#M3554</link>
      <description>&lt;P&gt;Agreed. I'm actually working on a version controlled, Continuous integration environment for a client. No direct updates on the Splunk environment. &lt;span class="lia-unicode-emoji" title=":grinning_face_with_smiling_eyes:"&gt;😄&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Jul 2015 16:02:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/set-up-an-account-for-splunk-developer/m-p/111484#M3554</guid>
      <dc:creator>alacercogitatus</dc:creator>
      <dc:date>2015-07-13T16:02:44Z</dc:date>
    </item>
  </channel>
</rss>

