Mutual SSL documented the wrong way
danizen opened this issue · comments
It is easy enough to find the example of configuring SSL in your feature to hit the backend. The problem with the demo is that this entirely the wrong way to do SSL. When I am running the test against a local server, the connection will not be SSL, and when I am targeting a remote server, the SSL certificates for mutual TLS may well be different for Dev, QA, and Prod.
Therefore, please update the demos for this so that you document how to setup mutual TLS in karate-config.js.
agreed, but concepts for karate-config.js are pretty clear and most teams extrapolate. it is hard for us to provide examples for all possible permutations. also if you have done this, please consider contributing to the examples
tagging this issue as help wanted contributions welcome
OK - Well, I have been unable to extrapolate. If you can tell me how I can configure ssl in my karate-config.js, I'll contribute to the examples. I've searched over the web, but nothing popped out at me.
This would actually help a lot - the CI/CD pipeline sends me the keystore password as an environment variable from Jenkins credentials, and since I'm doing the SSL configuration in each feature, I