I just installed the 3.2.0 and have problems clients connecting with TLS/SSL. The connection is not established. They are only able to make a plain log-in.
Just a question to the Certificates itself:
After installing (fresh install) and opening the server certificate page in the admin console, I was presented with a coloured bar that the certificates were changed and I had to restart so the http server can use those. I did , the restart was working proper. Is this on purpose as it generates certificates for the domain set for the server ?
By installing 3.1.1 I wasn’'t confronted with this and just used the provided certificates as in the package.
If the certificates were self-signed You can do following steps. Remove old certificates from keystore, run Wildfire and generate new, self-signed certfificates from admin console.
" run Wildfire and generate new, self-signed certfificates from admin console."
this is my problem. Just entering the info will create a new cert which I can use ? If that’'s the case, that should be easy. Let me know if I am correct here.
We have a proprietary client and found that the cert information coming back had the wrong length and the Microsoft libraries were attempting to parse a null pointer.
Don’'t know if that is helpful for the Pandion folks.