-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mutual SSL documented the wrong way #2534
Comments
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 |
OK - Well, I have been unable to extrapolate. If you can tell me how I can configure ssl in my |
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 |
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
.The text was updated successfully, but these errors were encountered: