<?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 Self-signed certificate without warnings? in Security</title>
    <link>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420906#M10003</link>
    <description>&lt;P&gt;Has anybody figured out how to use a self-signed certificate without getting a warning that it's invalid?&lt;BR /&gt;
I can access Splunk anyway and it does in fact use my certificate, but for the long haul I would want there to be no annoying warnings.&lt;BR /&gt;
I followed these instructions exactly:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/Self-signcertificatesforSplunkWeb"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/Self-signcertificatesforSplunkWeb&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/SecureSplunkWebusingasignedcertificate"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/SecureSplunkWebusingasignedcertificate&lt;/A&gt;&lt;BR /&gt;
I imported the myCACertificate.pem into Chrome by the way. &lt;BR /&gt;
It's also a testing environment with no live feeds.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Aug 2019 13:33:07 GMT</pubDate>
    <dc:creator>splunklearner12</dc:creator>
    <dc:date>2019-08-01T13:33:07Z</dc:date>
    <item>
      <title>Self-signed certificate without warnings?</title>
      <link>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420906#M10003</link>
      <description>&lt;P&gt;Has anybody figured out how to use a self-signed certificate without getting a warning that it's invalid?&lt;BR /&gt;
I can access Splunk anyway and it does in fact use my certificate, but for the long haul I would want there to be no annoying warnings.&lt;BR /&gt;
I followed these instructions exactly:&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/Self-signcertificatesforSplunkWeb"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/Self-signcertificatesforSplunkWeb&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/SecureSplunkWebusingasignedcertificate"&gt;https://docs.splunk.com/Documentation/Splunk/7.3.0/Security/SecureSplunkWebusingasignedcertificate&lt;/A&gt;&lt;BR /&gt;
I imported the myCACertificate.pem into Chrome by the way. &lt;BR /&gt;
It's also a testing environment with no live feeds.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 13:33:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420906#M10003</guid>
      <dc:creator>splunklearner12</dc:creator>
      <dc:date>2019-08-01T13:33:07Z</dc:date>
    </item>
    <item>
      <title>Re: Self-signed certificate without warnings?</title>
      <link>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420907#M10004</link>
      <description>&lt;P&gt;Chrome is telling me the certificate is invalid because it doesn't specify Subject Alternative Names.&lt;BR /&gt;
I tried following instructions from these two links:&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/476596/how-to-generate-csr-files-with-subjectaltnames-san.html" target="_blank"&gt;https://answers.splunk.com/answers/476596/how-to-generate-csr-files-with-subjectaltnames-san.html&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://www.hurricanelabs.com/splunk-tutorials/splunk-certificates-master-guide" target="_blank"&gt;https://www.hurricanelabs.com/splunk-tutorials/splunk-certificates-master-guide&lt;/A&gt;&lt;BR /&gt;
Basically, editing the file $SPLUNK_HOME/openssl/openssl.cnf to uncomment the line "req_extensions = v3_req" and included this under the stanza [v3_req]: subjectAltName=DNS:splunk.a.b.c.d, DNS:splunk, IP:127.0.0.1&lt;BR /&gt;
Obviously, a.b.c.d is replaced with the real domain. For info, I access splunk web using the internal URL &lt;A href="https://splunk:8000" target="_blank"&gt;https://splunk:8000&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:39:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420907#M10004</guid>
      <dc:creator>splunklearner12</dc:creator>
      <dc:date>2020-09-30T01:39:28Z</dc:date>
    </item>
    <item>
      <title>Re: Self-signed certificate without warnings?</title>
      <link>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420908#M10005</link>
      <description>&lt;P&gt;As a workaround, Firefox accepts the certificate with a green lock icon.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2019 15:13:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420908#M10005</guid>
      <dc:creator>splunklearner12</dc:creator>
      <dc:date>2019-08-07T15:13:26Z</dc:date>
    </item>
    <item>
      <title>Re: Self-signed certificate without warnings?</title>
      <link>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420909#M10006</link>
      <description>&lt;P&gt;Did you ever manage to add SAN into the pem? I have it in the csr, but not in the final pem. &lt;BR /&gt;
I assume it should be seen from the myCACertificate.pem file after this? Looks like it is not.&lt;/P&gt;

&lt;P&gt;/opt/splunk/bin/splunk cmd openssl x509 -req -in myCACertificate.csr -sha256 -signkey myCAPrivateKey.key -CAcreateserial -out myCACertificate.pem -days 3650&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2019 16:50:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Self-signed-certificate-without-warnings/m-p/420909#M10006</guid>
      <dc:creator>JykkeDaMan</dc:creator>
      <dc:date>2019-09-30T16:50:11Z</dc:date>
    </item>
  </channel>
</rss>

