just registered here since I want to share following info:
I’m currently running Openfire 3.6.4 with SparkWeb 0.9 on Windows (with IIS 6.0) and SSL/TLS encryption is working.
Not really sure what was needed in the end, since it took me a while and some testing until I got it running right.
Here’s the Openfire server settings that I think might be relevant,
Using above settings for openfire, (and having Ports 105, 106, 443 5222 and 9091 opened in my router’s firewall) SparkWeb works just fine, IF the required certificate is installed on the client machine.
Initially I wanted to make it possible for users with restricted connection to the internet (only port 80/443) to use SparkWeb with SSL too, but this did not work for me.
I think at least three open ports are needed for encryption to work, plus one port to access the webinterface itself - IIS with self-signed cert is listening on port 8080 and serving SparkWeb page requests on my system - due to 443 being used to enable at least unsecured login for those “proxy-victims”. Additionaly the same SparkWeb page is available on port 9091. Each webserver (IIS on port 8080 and the openfire web server on port 9091) has its own certificate which must be installed on the client side, and: trying to login to sparkweb from a non-HTTPS/“normal” HTTP webpage with “connectionType: https”, like below, doesn’t work for me - instead I need to go via the ssl-encrypted webpage to login using tls. Which is fine since users can decide through choice of login page if they want to login using TLS or unencrypted…
Here’s my working SparkWeb config for SSL:
Hope this will help somebody in some way,