<?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: Splunk Automatic Lookups and Capitlization in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303311#M12622</link>
    <description>&lt;P&gt;Will that work with CSV lookups or jsut KSV? I'm diong a pull from Active Directory, dropping it into a CSV file and then creating lookups&lt;/P&gt;</description>
    <pubDate>Wed, 04 Apr 2018 16:32:44 GMT</pubDate>
    <dc:creator>jmcclure</dc:creator>
    <dc:date>2018-04-04T16:32:44Z</dc:date>
    <item>
      <title>Splunk Automatic Lookups and Capitlization</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303309#M12620</link>
      <description>&lt;P&gt;What is a work around for case sensitive automatic lookups? I am trying to build out an automatic lookup for users and the users are all different types of capitilization. I am doing a pull from ldap dropping it into a CSV and then having a custom Splunk command execute a python script that  that duplicates every row with different user capitilization. BUT I still am having issues with one offs...&lt;/P&gt;

&lt;P&gt;I know caculated fields could work BUT they are after lookups in searchtime calculations&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2018 15:29:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303309#M12620</guid>
      <dc:creator>jmcclure</dc:creator>
      <dc:date>2018-04-04T15:29:30Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Automatic Lookups and Capitlization</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303310#M12621</link>
      <description>&lt;P&gt;See option for case_sensitive_match = &lt;/P&gt;

&lt;P&gt;In the lookups stanza for transforms.conf&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.0.3/Admin/Transformsconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/7.0.3/Admin/Transformsconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 18:46:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303310#M12621</guid>
      <dc:creator>starcher</dc:creator>
      <dc:date>2020-09-29T18:46:55Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Automatic Lookups and Capitlization</title>
      <link>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303311#M12622</link>
      <description>&lt;P&gt;Will that work with CSV lookups or jsut KSV? I'm diong a pull from Active Directory, dropping it into a CSV file and then creating lookups&lt;/P&gt;</description>
      <pubDate>Wed, 04 Apr 2018 16:32:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-Automatic-Lookups-and-Capitlization/m-p/303311#M12622</guid>
      <dc:creator>jmcclure</dc:creator>
      <dc:date>2018-04-04T16:32:44Z</dc:date>
    </item>
  </channel>
</rss>

