rmanaka Posted October 17, 2014 Posted October 17, 2014 Hi! Using ISY Dashboard Version 4.2.16 and Java version 8 Update 25. I am trying to generate a self-signed certificate for testing before I order a commercial certificate. (I am intending on ordering a UC certificate with SAN), but every time I try to generate the certificate I get a "Subject class type invalid" dialog box from JAVA which leads me to believe that the script is not working. I also note that the "Issuer" field is unavailable and does not self populate. Is the ISY certificate bad?
Techman Posted October 17, 2014 Posted October 17, 2014 rmanaka it's possible that java 8 is not yet supported by UDI. its official release is scheduled for early 2015. you may want to check with UDI tech support to see if this is causing your issue.
rmanaka Posted October 18, 2014 Author Posted October 18, 2014 rmanaka it's possible that java 8 is not yet supported by UDI. its official release is scheduled for early 2015. you may want to check with UDI tech support to see if this is causing your issue. That was it! Thanks @Techman!!! I reverted to Java version 7 update 71 and the self-signing certificate process worked just fine (without the ability to add SAN entries however). This was fine for my testing...I was able to test my SAN entries using the certificate generator on my Synology Disk Station(s). Hate to spend money on commercial certs until all of the parameters have been tested. UD Techsupport...might want to check on Java 8 compatibility with the dashboard.
larryllix Posted October 18, 2014 Posted October 18, 2014 (edited) I run Java 8 on a Win 7x64 system and also Java 7 on a Win 7x32 system. The Java 8 system has less problems with the Admin Console but mostly the same type of problems with the app sleeping or being backgrounded for a while. Java 8 has been updated on my system a few times now. Edited October 18, 2014 by larryllix
Michel Kohanim Posted October 19, 2014 Posted October 19, 2014 Hello all, Thanks so very much for the feedback. Indeed this is related to changes in Java 1.8 which changed the behavior of X509Certificate class. We are looking into this issue and will hopefully have it solved for the next release. With kind regards, Michel
Recommended Posts