<?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: Office365 - Azure Audit certificate failure (Red Hat with Proxy)  issue in All Apps and Add-ons</title>
    <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/559741#M66111</link>
    <description>&lt;P&gt;We have the similar issue too. So appending our own CA cert to the bottom of the&amp;nbsp;&lt;SPAN&gt;cacert.pem fixed our issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please note at our version (4.1.3) the&amp;nbsp;cacert.pem is located at&amp;nbsp;$SPLUNK_HOME/etc/apps/Splunk_TA_microsoft-cloudservices/lib/certifi/ folder. if you cannot find it at these folders, perhaps use any "find" command would do the trick.&lt;BR /&gt;&lt;BR /&gt;I think Splunk should document this workaround at the doc, as it is very common that companies would use their own company signed certificate for the Azure management endpoint.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 16 Jul 2021 04:02:14 GMT</pubDate>
    <dc:creator>season88481</dc:creator>
    <dc:date>2021-07-16T04:02:14Z</dc:date>
    <item>
      <title>Office365 - Azure Audit certificate failure (Red Hat with Proxy)  issue</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/330875#M39649</link>
      <description>&lt;P&gt;Hi, &lt;BR /&gt;
We are still getting errors even though we have added our Root CA and Intermediate CA to Red Hat's local certificate db. &lt;/P&gt;

&lt;P&gt;We are using Splunk_TA_microsoft-cloudservices v2.03 on Splunk Enterprise 6.6.2 running on Red Hat 7.4&lt;/P&gt;

&lt;P&gt;Root CA added to /etc/pki/ca-trust/source/anchors/company_root.pem (base64 encoded) &lt;BR /&gt;
Intermediate CA added to /etc/pki/ca-trust/source/anchors/company_int.pem (base64 encoded) &lt;/P&gt;

&lt;H1&gt;update-ca-trust&lt;/H1&gt;

&lt;P&gt;AuthenticationError: , SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:676)&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:43:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/330875#M39649</guid>
      <dc:creator>abalogh_splunk</dc:creator>
      <dc:date>2020-09-29T15:43:31Z</dc:date>
    </item>
    <item>
      <title>Re: Office365 - Azure Audit certificate failure (Red Hat with Proxy)  issue</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/330876#M39650</link>
      <description>&lt;P&gt;I will answer my own question because this was not documented. I had to read code. &lt;/P&gt;

&lt;P&gt;The correct certificate file to update with your Root CA and intermediate CA (which we need since we are inspecting SSL traffic) was: &lt;/P&gt;

&lt;P&gt;Splunk_TA_microsoft-cloudservices/bin/splunktamscs/certify/cacert.pem &lt;/P&gt;

&lt;P&gt;We appended the /etc/pki/tls/certs/ca-bundle.crt to Splunk_TA_microsoft-cloudservices/bin/splunktamscs/certify/cacert.pem and started working. &lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:43:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/330876#M39650</guid>
      <dc:creator>abalogh_splunk</dc:creator>
      <dc:date>2020-09-29T15:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: Office365 - Azure Audit certificate failure (Red Hat with Proxy)  issue</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/542762#M65061</link>
      <description>&lt;P&gt;This fixed the problem that I was facing. Thanks for posting.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Mar 2021 00:13:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/542762#M65061</guid>
      <dc:creator>laurie_gellatly</dc:creator>
      <dc:date>2021-03-08T00:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: Office365 - Azure Audit certificate failure (Red Hat with Proxy)  issue</title>
      <link>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/559741#M66111</link>
      <description>&lt;P&gt;We have the similar issue too. So appending our own CA cert to the bottom of the&amp;nbsp;&lt;SPAN&gt;cacert.pem fixed our issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please note at our version (4.1.3) the&amp;nbsp;cacert.pem is located at&amp;nbsp;$SPLUNK_HOME/etc/apps/Splunk_TA_microsoft-cloudservices/lib/certifi/ folder. if you cannot find it at these folders, perhaps use any "find" command would do the trick.&lt;BR /&gt;&lt;BR /&gt;I think Splunk should document this workaround at the doc, as it is very common that companies would use their own company signed certificate for the Azure management endpoint.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jul 2021 04:02:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/All-Apps-and-Add-ons/Office365-Azure-Audit-certificate-failure-Red-Hat-with-Proxy/m-p/559741#M66111</guid>
      <dc:creator>season88481</dc:creator>
      <dc:date>2021-07-16T04:02:14Z</dc:date>
    </item>
  </channel>
</rss>

