<?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: Deployment server https - no client certificate in Security</title>
    <link>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749613#M18459</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/224371"&gt;@lux209&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is not required to use mTLS if you do not want to (I dont usually have mTLS on client-&amp;gt;DS comms as for using SSL is enough for me).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Set in the server.conf set [sslConfig]/&lt;SPAN&gt;requireClientCert stanza to false (which I think is the default).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For me the reason you might want to use clientCert on a DS is if you wanted to ensure that no other hosts could connect to your DS and receive its configuration, which may contain sensitive credentials/configurations (e.g. certs to send to your indexers). If this is low risk for you (e.g. not publicly accessible) then it sounds like having&amp;nbsp;&lt;SPAN&gt;requireClientCert to false would suffice.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
    <pubDate>Fri, 11 Jul 2025 10:14:40 GMT</pubDate>
    <dc:creator>livehybrid</dc:creator>
    <dc:date>2025-07-11T10:14:40Z</dc:date>
    <item>
      <title>Deployment server https - no client certificate</title>
      <link>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749610#M18458</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I'm looking to secure the connection to our deployment server using HTTPS following this doc:&lt;BR /&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.4.2/Security/Securingyourdeploymentserverandclients" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.4.2/Security/Securingyourdeploymentserverandclients&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I'm wondering if having client certificate is mandatory or if it would be possible to only install a certificate on the DS server itself ? I don't need the to have mTLS, my goal is only to have an encrypted connection between the server and the clients.&lt;/P&gt;&lt;P&gt;Thanks for you help&lt;BR /&gt;Lucas&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 09:28:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749610#M18458</guid>
      <dc:creator>lux209</dc:creator>
      <dc:date>2025-07-11T09:28:39Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment server https - no client certificate</title>
      <link>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749613#M18459</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/224371"&gt;@lux209&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is not required to use mTLS if you do not want to (I dont usually have mTLS on client-&amp;gt;DS comms as for using SSL is enough for me).&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Set in the server.conf set [sslConfig]/&lt;SPAN&gt;requireClientCert stanza to false (which I think is the default).&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;For me the reason you might want to use clientCert on a DS is if you wanted to ensure that no other hosts could connect to your DS and receive its configuration, which may contain sensitive credentials/configurations (e.g. certs to send to your indexers). If this is low risk for you (e.g. not publicly accessible) then it sounds like having&amp;nbsp;&lt;SPAN&gt;requireClientCert to false would suffice.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-unicode-emoji" title=":glowing_star:"&gt;🌟&lt;/span&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;Did this answer help you?&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;If so, please consider:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Adding karma to show it was useful&lt;/LI&gt;&lt;LI&gt;Marking it as the solution if it resolved your issue&lt;/LI&gt;&lt;LI&gt;Commenting if you need any clarification&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Your feedback encourages the volunteers in this community to continue contributing&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 10:14:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749613#M18459</guid>
      <dc:creator>livehybrid</dc:creator>
      <dc:date>2025-07-11T10:14:40Z</dc:date>
    </item>
    <item>
      <title>Re: Deployment server https - no client certificate</title>
      <link>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749619#M18461</link>
      <description>&lt;P&gt;Great thank you for the quick answer and the information !&lt;BR /&gt;&lt;BR /&gt;Lucas&lt;/P&gt;</description>
      <pubDate>Fri, 11 Jul 2025 10:51:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Deployment-server-https-no-client-certificate/m-p/749619#M18461</guid>
      <dc:creator>lux209</dc:creator>
      <dc:date>2025-07-11T10:51:07Z</dc:date>
    </item>
  </channel>
</rss>

