cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Who Me Too'd this topic

Notice of PAN-OS SSL Certificate Expiration

Retired Member
Not applicable

Note: This notice applies to customers with WF-500, WildFire Cloud, and PAN-DB.

 

This notification is to provide you advance notice that the SSL certificates used by PAN-OS/Panorama to authenticate to the WF-500 appliance, to the WildFire public cloud service, and to the PAN-DB URL filtering service will expire on January 21, 2016 18:23:01 UTC.

 

Following the expiration, PAN-OS/Panorama devices that have not been updated will not be able to communicate with those services.


To ensure service continuity for WildFire and PAN-DB, all users are advised to complete one of the following steps:

 

   1.  Install content version 550 (or later).

 

OR

 

  1.  Upgrade your PAN-OS/Panorama version to one of the below releases. Guidance is available on our support site here

        • 5.0.17

        • 5.1.11 (scheduled for week of Jan. 11, 2016)

        • 6.0.12

        • 6.1.9 (scheduled for week of Jan. 11, 2016)

        • 7.0.4

 

If you have any questions regarding this notification, content releases, or the upgrade process, please don’t hesitate to reach out to your support provider or Palo Alto Networks Customer Support at +1 408.738.7799 or visit https://live.paloaltonetworks.com/t5/custom/page/page-id/Support.


Thank you,
The Palo Alto Networks Support Team

 

 

Caveats

  • If User-ID agents are deployed, a restart of the User-ID service may be required after the upgrade to content version 550 (or later) using the following command:
PAN-OS 7.0 and later
> debug software restart process user-id

prior to PAN-OS 7.0
> debug software restart user-id
  • If a system is upgraded after applying content package 550 (or later) to a PAN-OS version lower than the abovementioned PAN-OS versions (for example, 6.1.7 is upgraded to 6.1.8 instead of .9), the content package needs to be re-installed for the new certificate to be applied.
Who Me Too'd this topic