Great question, and thank you for providing the link.
FMS 13 is unlikely to be affected, as I do not believe that it has any need to utilize Java WebStart, thanks to the new admin console.
With respect to FMS 12, I note that FMI released an update to FMS 12: 12.0.5, which apparently was an update specifically to address the issue of the jar file (for the admin console) needing to have the Permissions attribute in the jar's manifest file.
Reading the Oracle article that you linked to, the only other criteria to be concerned about at this time would be whether or not the code for the FMS 12 admin console is signed.
I realize that this is not a complete answer to your question, but I hope it helps.
Very best regards,
Very relevant thread. I have gotten used to checking here before updating.
For me, with FMS 12.0.3 installed, and not willing to bother updating to 12.0.5, I will skip this Java update. But always interested in hearing if it WOULD work...
I have a mac mini running FMS 11, and after updating java on my laptop, I had to manually add the server's address in the exception list under the Java Control Panel Security tab to be able to launch the FM server admin console again. Another solution that worked as well is setting the security level to "medium" instead of high.