
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2021 03:22 AM
Hello,
I was working on a ISE 2.4 deployment (patch 5) and found that the CA signed certificates were expired. Strangely, the ISE admin, portal, RADIUS etc. services were accessible. From what I read, this shouldnt happen.
Ultimately, the moment I tried to install the latest patch, ISE restarted its services and ISE nodes stopped communicating within the deployment.
Wonder what caused the nodes to keep running even after certificate expiry?
Any insight/information would be great.
Regards,
Girish
Solved! Go to Solution.
- Labels:
-
Identity Services Engine (ISE)
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 01:58 PM
All ISE portals and services will continue to function even with default self-signed or expired certificates. RADIUS and TACACS may function without CA-signed certificates.
Your endpoints and/or users, however, may not decide trust ISE as an authentication server depending on the supplicant configuration or risk tolerance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 01:58 PM
All ISE portals and services will continue to function even with default self-signed or expired certificates. RADIUS and TACACS may function without CA-signed certificates.
Your endpoints and/or users, however, may not decide trust ISE as an authentication server depending on the supplicant configuration or risk tolerance.
