<?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: How do I Embed Splunk SSL cert in client application? in Security</title>
    <link>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423071#M12981</link>
    <description>&lt;P&gt;@tesme,&lt;/P&gt;

&lt;P&gt;The error says that the the IP you are trying to connect is not part of the Subject Alternative Names (SAN).&lt;BR /&gt;
SSL needs identification of the peer, otherwise your connection might be against a man-in-the-middle which decrypts + sniffs/modifies the data and then forwards them encrypted again to the real target. Identification is done with x509 certificates which need to be validated against a trusted CA and which need to identify the target you want to connect to.&lt;/P&gt;

&lt;P&gt;Usually the target is given as a hostname and this is checked against the subject and subject alternative names of the certificate. In this case your target is a IP. To validate the certificate successfully the IP must be given in the certificate inside the subject alternative names section, but not as an DNS entry (e.g. hostname) but instead as IP.&lt;/P&gt;

&lt;P&gt;You could try connecting with hostname or create new certificate pairs. If you are at a home network, probably you could disable the hostname verification from the client side or disable the ssl (not recommended though)&lt;/P&gt;</description>
    <pubDate>Wed, 22 Aug 2018 03:57:56 GMT</pubDate>
    <dc:creator>renjith_nair</dc:creator>
    <dc:date>2018-08-22T03:57:56Z</dc:date>
    <item>
      <title>How do I Embed Splunk SSL cert in client application?</title>
      <link>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423070#M12980</link>
      <description>&lt;P&gt;My program has a variable, a string that contains the Splunk PEM certificate. Every request that is sent to the API includes my program verifying the cert being presented by the Splunk server is the one in the application. Okay so the error message I get is that:&lt;BR /&gt;
"Couldn't login to splunk: Post &lt;A href="https://10.0.0.18:8089/services/auth/login:"&gt;https://10.0.0.18:8089/services/auth/login:&lt;/A&gt; x509: cannot validate certificate for 10.0.0.18 because it doesn't contain any IP SANs"&lt;/P&gt;

&lt;P&gt;What am I missing here? There must be something about the Splunk architecture I am missing as related to certificates. BTW this is a FREE spunk server I am running at home.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Aug 2018 19:48:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423070#M12980</guid>
      <dc:creator>tesme</dc:creator>
      <dc:date>2018-08-21T19:48:03Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Embed Splunk SSL cert in client application?</title>
      <link>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423071#M12981</link>
      <description>&lt;P&gt;@tesme,&lt;/P&gt;

&lt;P&gt;The error says that the the IP you are trying to connect is not part of the Subject Alternative Names (SAN).&lt;BR /&gt;
SSL needs identification of the peer, otherwise your connection might be against a man-in-the-middle which decrypts + sniffs/modifies the data and then forwards them encrypted again to the real target. Identification is done with x509 certificates which need to be validated against a trusted CA and which need to identify the target you want to connect to.&lt;/P&gt;

&lt;P&gt;Usually the target is given as a hostname and this is checked against the subject and subject alternative names of the certificate. In this case your target is a IP. To validate the certificate successfully the IP must be given in the certificate inside the subject alternative names section, but not as an DNS entry (e.g. hostname) but instead as IP.&lt;/P&gt;

&lt;P&gt;You could try connecting with hostname or create new certificate pairs. If you are at a home network, probably you could disable the hostname verification from the client side or disable the ssl (not recommended though)&lt;/P&gt;</description>
      <pubDate>Wed, 22 Aug 2018 03:57:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423071#M12981</guid>
      <dc:creator>renjith_nair</dc:creator>
      <dc:date>2018-08-22T03:57:56Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Embed Splunk SSL cert in client application?</title>
      <link>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423072#M12982</link>
      <description>&lt;P&gt;How do you recommend adding in an IP SAN while creating a new self signed certificate in Splunk?&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 23:27:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423072#M12982</guid>
      <dc:creator>tesme</dc:creator>
      <dc:date>2018-08-28T23:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: How do I Embed Splunk SSL cert in client application?</title>
      <link>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423073#M12983</link>
      <description>&lt;P&gt;By the way, I am running a free splunk instance in virtual box.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 23:42:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-do-I-Embed-Splunk-SSL-cert-in-client-application/m-p/423073#M12983</guid>
      <dc:creator>tesme</dc:creator>
      <dc:date>2018-08-28T23:42:38Z</dc:date>
    </item>
  </channel>
</rss>

