1. Starting xxeserver on Linux or on macOS Previous topic Parent topic Child topic Next topic

Let's suppose XMLmind XML Editor Web Edition (XXEW) has been installed in /opt/xxe/ and that SSL certificate cert_192_168_1_203.pfx (where 192.168.1.203 is the IP address of your computer) has been copied to /opt/xxe/web/etc/.
/opt/xxe/web/bin$ nohup xxeserver -pid ../var/xxeserver.pid \
      -keystore ../etc/cert_192_168_1_203.pfx \
      -storepass changeit -keypass changeit \
      -logserver ../var/srv \
      > /dev/null 2>&1 &
If you don't have an actual SSL certificate, option -selfsign lets you quickly generate a self-signed one.
/opt/xxe/web/bin$ nohup xxeserver -pid ../var/xxeserver.pid \
      -selfsign "CN=192.168.1.203,O=ACME Corp." ../etc/selfsign_192_168_1_203.pfx \
      -logserver ../var/srv \
      > /dev/null 2>&1 &
Of course, with a self-signed SSL certificate, all web browsers will report a security issue.

Figure 5-2. Google Chrome reporting a security issue related to an SSL certificate

web_browser_cert_warn.png
The user of the web browser will have to click Advanced and then "Proceed to xxeserver_address (unsafe)" to be able to load the HTML page containing xxeserver client (which is the sample XML Editor in this example). Generally this confirmation must be made just once, the first time you'll load the HTML page containing the client. After that, the web browser will store your self-signed SSL certificate as a “security exception”.

Figure 5-3. Google Chrome letting you accept the self-signed SSL certificate

web_browser_cert_proceed.png