Thanks Xeonkeeper. Did you use open SSL to generate the new self-signed cert?
No, we used our wildacard certificate from a public certificate authority.
I'm not going to say you can't do this since the product is End of Life and End of Support. But I don't recommend it. If you log in to the underlying OS and break something you're going to have no support to fall back on and could end up with a totally non-functioning system.
Email me at firstname.lastname@example.org and we will set up a date and time. I work from 8:00 am - 4:30 pm EST (GMT-5).
we need your help too. Can we also arrange an appointment for a remote session.
Many thanks for all...
Hi Mike! I have followed the thread and beg for your help as well. I already sent you an email asking for help. Hope you are able to rescue us. Regards ... Ana Maria
We also had a problem with login cma desktop after expired certificate in February.
We fix it in simple way. Just change date in computer for example 2015.
Now cma desktop works.
Which date did you change? The CMA4000 or the client device? I tried both, but without any success. Could you be a little more explicit. Thank you very much.
Hmmm. This is reminding me of an issue with CMAD from back in May of 2013. There was an internal openDS keystore file that needed to be replaced. One of the workarounds was to change the date on the PC. I'm starting to wonder if that's related to some of the issues I have had updating the Apache self-signed certificate. The update itself works fine and both the browser and the CMA application show an expiration date of the certificate in 2029 but CMAD clients are failing to log in.