<?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: SSL certificate expiring soon in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289640#M77011</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;yeah, this is what I thought but was trying to find any other ideal solutions. I think I'll go ahead with this solution unless any of our memebers suggest otherwise.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Sep 2019 18:39:37 GMT</pubDate>
    <dc:creator>SThatipelly</dc:creator>
    <dc:date>2019-09-23T18:39:37Z</dc:date>
    <item>
      <title>SSL certificate expiring soon</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289543#M76995</link>
      <description>&lt;P&gt;I have a wildcard cert issued by godaddy which I use for inbound decryption on approx 10 dmz servers. it is set to expire soon and we've got a new cert. how can I seamlessly import it and not break the client connections as my server admins servers&amp;nbsp; cannot replace the cert on all of them&amp;nbsp; at same time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2019 13:37:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289543#M76995</guid>
      <dc:creator>SThatipelly</dc:creator>
      <dc:date>2019-09-23T13:37:58Z</dc:date>
    </item>
    <item>
      <title>Re: SSL certificate expiring soon</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289631#M77009</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/70284"&gt;@SThatipelly&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;So when you import the new certificate you'll name it something different than your current certificate. Then as your server admins update the certificate that the server is using you'll update that servers decryption rulebase entry to use the new certificate instead of the old certificate.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;- If you have all of these servers in one single decryption entry you'll want to separate them out so that each server gets it's own policy. This will simplify actually changing things as services are switched to the new certificate.&lt;/P&gt;&lt;P&gt;- You really can't do this without at least a brief outage for each service, so plan accordingly.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2019 18:17:17 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289631#M77009</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-09-23T18:17:17Z</dc:date>
    </item>
    <item>
      <title>Re: SSL certificate expiring soon</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289640#M77011</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/43480"&gt;@BPry&lt;/a&gt;&amp;nbsp;yeah, this is what I thought but was trying to find any other ideal solutions. I think I'll go ahead with this solution unless any of our memebers suggest otherwise.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2019 18:39:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/ssl-certificate-expiring-soon/m-p/289640#M77011</guid>
      <dc:creator>SThatipelly</dc:creator>
      <dc:date>2019-09-23T18:39:37Z</dc:date>
    </item>
  </channel>
</rss>

