<?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: Port issue with splunkd SSL in Security</title>
    <link>https://community.splunk.com/t5/Security/Port-issue-with-splunkd-SSL/m-p/334495#M8529</link>
    <description>&lt;P&gt;Ok, answering my own question. One way to contribute. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Need to set the following env var:&lt;BR /&gt;
SPLUNKD_URI &lt;BR /&gt;
to the FQDN of your machine. Then it will work.&lt;/P&gt;</description>
    <pubDate>Thu, 14 Sep 2017 14:31:39 GMT</pubDate>
    <dc:creator>irsysintegratio</dc:creator>
    <dc:date>2017-09-14T14:31:39Z</dc:date>
    <item>
      <title>Port issue with splunkd SSL</title>
      <link>https://community.splunk.com/t5/Security/Port-issue-with-splunkd-SSL/m-p/334494#M8528</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;We want to enable Splunkd SSL, so we put &lt;BR /&gt;
enableSplunkdSSL = true&lt;BR /&gt;
to server.conf.&lt;BR /&gt;
We generated a certificate using the FQDN as the CN of the certificate. &lt;/P&gt;

&lt;P&gt;Then in our AddOn, we use splunk.getLocalServerInfo() to get the url:port. The problem is that splunk.getLocalServerInfo() always returns &lt;A href="https://127.0.0.1:8089"&gt;https://127.0.0.1:8089&lt;/A&gt;, even if we changed MgmtHostPort in web.conf. As a result, we always get an error:&lt;BR /&gt;
SSLError: hostname '127.0.0.1' doesn't match xxxxxx, where xxxxxx is the CN we set for the certificate.&lt;/P&gt;

&lt;P&gt;So how shall this work? Shall we use 127.0.0.1 as the CN to create a cert? Or we shall not call getLocalServerInfo()?&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 13 Sep 2017 21:21:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Port-issue-with-splunkd-SSL/m-p/334494#M8528</guid>
      <dc:creator>irsysintegratio</dc:creator>
      <dc:date>2017-09-13T21:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: Port issue with splunkd SSL</title>
      <link>https://community.splunk.com/t5/Security/Port-issue-with-splunkd-SSL/m-p/334495#M8529</link>
      <description>&lt;P&gt;Ok, answering my own question. One way to contribute. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;Need to set the following env var:&lt;BR /&gt;
SPLUNKD_URI &lt;BR /&gt;
to the FQDN of your machine. Then it will work.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Sep 2017 14:31:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Port-issue-with-splunkd-SSL/m-p/334495#M8529</guid>
      <dc:creator>irsysintegratio</dc:creator>
      <dc:date>2017-09-14T14:31:39Z</dc:date>
    </item>
  </channel>
</rss>

