<?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 Is it possible to use the same certificate for web UI access and data forwarding? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-use-the-same-certificate-for-web-UI-access-and/m-p/460474#M79483</link>
    <description>&lt;P&gt;As in title, I was wondering if it is possible to use the same certificate on Heavy forwarders for access to the web UI and as a server cert for server forwarding.&lt;/P&gt;

&lt;P&gt;looking at here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.1/Security/Howtogetthird-partycertificates"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.1/Security/Howtogetthird-partycertificates&lt;/A&gt;&lt;BR /&gt;
and here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/Security/Getthird-partycertificatesforSplunkWeb"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.2/Security/Getthird-partycertificatesforSplunkWeb&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The process for creating the CSRs is a bit different. In the web certificate the password is removed from the key before creating the CSR. would that make any difference on the final certificate? would I be able to use it for both functions? Is there something that I might need to be aware of?&lt;/P&gt;</description>
    <pubDate>Fri, 27 Mar 2020 17:35:10 GMT</pubDate>
    <dc:creator>konstr</dc:creator>
    <dc:date>2020-03-27T17:35:10Z</dc:date>
    <item>
      <title>Is it possible to use the same certificate for web UI access and data forwarding?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-use-the-same-certificate-for-web-UI-access-and/m-p/460474#M79483</link>
      <description>&lt;P&gt;As in title, I was wondering if it is possible to use the same certificate on Heavy forwarders for access to the web UI and as a server cert for server forwarding.&lt;/P&gt;

&lt;P&gt;looking at here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.1/Security/Howtogetthird-partycertificates"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.1/Security/Howtogetthird-partycertificates&lt;/A&gt;&lt;BR /&gt;
and here: &lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.2/Security/Getthird-partycertificatesforSplunkWeb"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.2/Security/Getthird-partycertificatesforSplunkWeb&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The process for creating the CSRs is a bit different. In the web certificate the password is removed from the key before creating the CSR. would that make any difference on the final certificate? would I be able to use it for both functions? Is there something that I might need to be aware of?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 17:35:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Is-it-possible-to-use-the-same-certificate-for-web-UI-access-and/m-p/460474#M79483</guid>
      <dc:creator>konstr</dc:creator>
      <dc:date>2020-03-27T17:35:10Z</dc:date>
    </item>
  </channel>
</rss>

