This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
Public view shows Status "Open", but I was told internally it was declined. Since ISE is near to feature parity with ACS, it (ACS) will be EOL soon (I would expect EOL notice this year). There seems to be no plans to implement any new features in ACS.
Yes, it is supported in ACS 5.8 and it works. BUT, we have some trouble when we made the upgrade, in the step of passing to patch 4. The services were working but the ACS was not accesible by GUI. We have to call Cisco TAC in order to get this resolved. This happened twice in 3 days, making the upgrade for 2 different ACS.
Thank you for updating! Can you please tell us some details about your problem and the solution TAC provided to you?
Was it just the management process which did not finish starting and you were told to restart it (we had this sometimes in the past during updates)?
Or was it more complicated?
Cisco TAC modified a database table, which was only accesible using the root password; which Cisco TAC didnt want to give to us. All the process took near 20 minutes. After the first upgrade they suggested us to call them if we have the same problem in the next upgrade, which happened 3 days later.
Sorry for late reply and thanks Tobias to pitch in.
The last date that Cisco Engineering may release any final software maintenance releases or bug fixes is end of 2017. However, looking at ISE development I don't think if work will be done to add support for TLS 1.2