<?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 How does Splunk DB Connect identity.dat file gets generated? in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-does-Splunk-DB-Connect-identity-dat-file-gets-generated/m-p/586095#M76141</link>
    <description>&lt;P&gt;We are working on automating the installation and configuration of Splunk DB Connect.&amp;nbsp; For the purposes of this question we are using DB Connect version 3.6.0&lt;/P&gt;
&lt;P&gt;My question is how does the identity.dat file get generated.&amp;nbsp; We know it gets generated on a fresh DB Connect install the first time an identity is created manually.&amp;nbsp; Our issue is the DB Connect API endpoint for creating identities returns a 200 OK when creating an identity for the first time - but it does not get created and no identity.dat file is generated.&lt;/P&gt;
&lt;P&gt;If after a fresh install of DB Connect we manually though the UI add an identity - the identity.dat file is successfully generated.&amp;nbsp; We are then able to hit the endpoint to create identities and it creates them correctly.&lt;/P&gt;
&lt;P&gt;The endpoint that we are hitting is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/servicesNS/nobody/splunk_app_db_connect/db_connect/dbxproxy/identities&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The payload that we are uploading to the endpoint is formatted as such:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;    def output(self):
        data = {}
        data["name"] = self.db_identity_name
        data["username"] = self.db_username
        data["password"] = self.db_password
        data["disabled"] = self.disabled
        data["domain_name"] = self.domain_name
        data["use_win_auth"] = self.use_win_auth
        return data&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 22 Feb 2022 18:51:35 GMT</pubDate>
    <dc:creator>mchristopherson</dc:creator>
    <dc:date>2022-02-22T18:51:35Z</dc:date>
    <item>
      <title>How does Splunk DB Connect identity.dat file gets generated?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-does-Splunk-DB-Connect-identity-dat-file-gets-generated/m-p/586095#M76141</link>
      <description>&lt;P&gt;We are working on automating the installation and configuration of Splunk DB Connect.&amp;nbsp; For the purposes of this question we are using DB Connect version 3.6.0&lt;/P&gt;
&lt;P&gt;My question is how does the identity.dat file get generated.&amp;nbsp; We know it gets generated on a fresh DB Connect install the first time an identity is created manually.&amp;nbsp; Our issue is the DB Connect API endpoint for creating identities returns a 200 OK when creating an identity for the first time - but it does not get created and no identity.dat file is generated.&lt;/P&gt;
&lt;P&gt;If after a fresh install of DB Connect we manually though the UI add an identity - the identity.dat file is successfully generated.&amp;nbsp; We are then able to hit the endpoint to create identities and it creates them correctly.&lt;/P&gt;
&lt;P&gt;The endpoint that we are hitting is:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;/servicesNS/nobody/splunk_app_db_connect/db_connect/dbxproxy/identities&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The payload that we are uploading to the endpoint is formatted as such:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;LI-CODE lang="python"&gt;    def output(self):
        data = {}
        data["name"] = self.db_identity_name
        data["username"] = self.db_username
        data["password"] = self.db_password
        data["disabled"] = self.disabled
        data["domain_name"] = self.domain_name
        data["use_win_auth"] = self.use_win_auth
        return data&lt;/LI-CODE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 18:51:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-does-Splunk-DB-Connect-identity-dat-file-gets-generated/m-p/586095#M76141</guid>
      <dc:creator>mchristopherson</dc:creator>
      <dc:date>2022-02-22T18:51:35Z</dc:date>
    </item>
    <item>
      <title>Re: How does Splunk DB Connect identity.dat file gets generated?</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-does-Splunk-DB-Connect-identity-dat-file-gets-generated/m-p/586105#M76142</link>
      <description>&lt;P&gt;This file gets auto generated.&amp;nbsp; It helps if your filesystem level permissions are set correctly so the user and group running splunk own the splunk_app_db_connect directory and sub-directories.&amp;nbsp; We had an issue with our ansible where these were being set to root:root instead of splunk:splunk.&lt;/P&gt;&lt;P&gt;Once we resolved that issue the indentity.dat file auto generates when splunk starts up.&amp;nbsp; The 200 OK's were still concerning to get when hitting the API even though no identity was actually created.&lt;/P&gt;</description>
      <pubDate>Tue, 22 Feb 2022 20:34:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/How-does-Splunk-DB-Connect-identity-dat-file-gets-generated/m-p/586105#M76142</guid>
      <dc:creator>mchristopherson</dc:creator>
      <dc:date>2022-02-22T20:34:35Z</dc:date>
    </item>
  </channel>
</rss>

