When using BlazeVSE on Docker, all SSL/TLS traffic will be handled directly (as is the case with DevTest VSE).
To provide your own SSL certificate/keystore on your VSM, you can either:
- Include the keystore in your MAR project and have your listen step reference this file
- Include the keystore in a path that is relative to LISA_HOME (which is /devtest in the case of BlazeVSE)
By default, BlazeVSE and the listen steps in VSMs will look for the SSL keystore based on the resolved value of the ssl.server.cert.path property. (defaults to in the {{LISA_HOME}}/vse.ks file). You could either upload a replacement of this file, or you can upload it under a different name and set the ssl.server.cert.path and ssl.server.cert.pass properties
You can then set the following values in your local.properties overrides in the BlazeVSE Environments tab:
ssl.server.cert.path={{LISA_HOME}}myKeystoreFile.jks
ssl.server.cert.pass=keyStorePasswordUnencrypted