1 SlimerJS + CAS + self-signed certificate

The following guide is inspired by and extends it with more details.

SlimerJS (as of 0.8.3) lacks the commandline options to say "relax about bad certificates". Unfortunately the self-signed SSL certificate, that developers typically use during development, counts as a bad certificate.

  1. SlimerJS folder is deflated on Windows in %AppData%\Local\Temp\java-slimerjs\slimerjs-0.9.6-win32.
      From there you can launch SlimerJS executable file in order to create a profile.
      (You can call your new profile anything, "AllowSSL" is just for example.)

 slimerjs.bat --createprofile AllowSSL --debug=yes

  The "debug" option seems mandatory on Windows in order to get an output.
  Make a note of the directory it has created. E.g. %AppData%\Roaming\Innophi\SlimerJS\Profiles\bpm7ktki.AllowSSL

2. Open Firefox, browse to Knowage URL, add it as a security exception.
  If you have been testing your website already, maybe you've already done this and you can skip this step.

3. Go to your Firefox profile, and look for the file called "cert_override.txt".
  E.g. %AppData%\Roaming\Mozilla\Firefox\Profiles\4izf6nuy.default
  Copy that to the directory you created in step 1.

4. Have a look at the copy you just made of "cert_override.txt".
  If it only has the entry you added in step 2, you are done.
  Otherwise, remove the entries you don't want.
  (The file format is easy: one certificate per line.)

5. Now when you need to run SlimerJS Knowage must run it with the "-P AllowSSL" commandline parameter.
  E.g. slimerjs -P AllowSSL httpstest.js

Created by Francesco Lucchi on 2017/06/26 16:42
Last modified by Francesco Lucchi on 2017/06/26 16:59

This wiki is licensed under a Creative Commons 2.0 license
XWiki Enterprise 2.7.33694 - Documentation