<?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: Linux: Splunk Universal Forwarder as non-root with supplementary groups in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517286#M6629</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;local groups are working for me as well. The problem is only with groups from ldap.&lt;/P&gt;&lt;P&gt;Did you try with ldap groups?&lt;/P&gt;&lt;P&gt;And: Did you really try to run my script as a real scripted input via inputs.conf and not over regular cli?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Lorenz&lt;/P&gt;</description>
    <pubDate>Tue, 01 Sep 2020 15:42:38 GMT</pubDate>
    <dc:creator>DATEVeG</dc:creator>
    <dc:date>2020-09-01T15:42:38Z</dc:date>
    <item>
      <title>Linux: Splunk Universal Forwarder as non-root with supplementary groups</title>
      <link>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517238#M6627</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;our splunk&amp;nbsp; universal forwarder is runnning under a non-root service account, which is defined in our central ldap.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We upgraded our universal forwarder from 7.3.7 to 8.0.5 and now&amp;nbsp;our forwarder cannot monitor our file anymore.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The file to be monitored is set as following:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;#ls -al /tmp/ldap-group-test&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;-rw-r-----. 1 root ldapgroup 100 Sep 1 09:27 /tmp/ldap-group-test&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Our splunk service account user is a member of the group ldapgroup:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;#id ldapsplunk&lt;BR /&gt;uid=100007(ldapsplunk) gid=100008(ldapsplunkgroup) groups=100008(ldapsplunkgroup),100009(ldapgroup)&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Splunk with a universal forwarder in version 8.0.5 we get a permission denied.&lt;/P&gt;&lt;P&gt;If we use a scripted input (inputs.conf) to display the user and group context of the currently running splunk forwarder session:&lt;/P&gt;&lt;P&gt;bin/display_groups.sh&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;#/bin/bash&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;hostname=$(hostname)&lt;BR /&gt;time=$(date +%s)&lt;BR /&gt;id=$(id)&lt;BR /&gt;rc=$?&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;echo "${time} - ${hostname} - ${id} - ${rc}"&lt;/P&gt;&lt;P&gt;we get as output:&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;1598967093 - splunkhost.bla.fasel.de - uid=100007(ldapsplunk) gid=100008(ldapsplunkgroup) groups=100008(ldapsplunkgroup) context=system_u:system_r:unconfined_service_t:s0 - 0&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As you can see, the membership of&amp;nbsp;ldapgroup is missing here.&lt;/P&gt;&lt;P&gt;It seems that during the start process of the universal forwarder, the permissions for ldap groups aren't passed correctly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone already noticed this? Are there any workarounds other than downgrading to version 7.3?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;- Lorenz&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 13:56:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517238#M6627</guid>
      <dc:creator>DATEVeG</dc:creator>
      <dc:date>2020-09-01T13:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Linux: Splunk Universal Forwarder as non-root with supplementary groups</title>
      <link>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517247#M6628</link>
      <description>&lt;P&gt;I have tested your scenario, my splunk is running with user splunk and group splunk&lt;/P&gt;&lt;P&gt;I have created a new group added user to new group also.&lt;/P&gt;&lt;P&gt;I have created test.sh with code you shared.&lt;/P&gt;&lt;P&gt;when I ran test.sh using splunk cmd bash test.sh&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can see old group and new group.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't that is an issue with Splunk.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 14:40:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517247#M6628</guid>
      <dc:creator>thambisetty</dc:creator>
      <dc:date>2020-09-01T14:40:40Z</dc:date>
    </item>
    <item>
      <title>Re: Linux: Splunk Universal Forwarder as non-root with supplementary groups</title>
      <link>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517286#M6629</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;local groups are working for me as well. The problem is only with groups from ldap.&lt;/P&gt;&lt;P&gt;Did you try with ldap groups?&lt;/P&gt;&lt;P&gt;And: Did you really try to run my script as a real scripted input via inputs.conf and not over regular cli?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- Lorenz&lt;/P&gt;</description>
      <pubDate>Tue, 01 Sep 2020 15:42:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Linux-Splunk-Universal-Forwarder-as-non-root-with-supplementary/m-p/517286#M6629</guid>
      <dc:creator>DATEVeG</dc:creator>
      <dc:date>2020-09-01T15:42:38Z</dc:date>
    </item>
  </channel>
</rss>

