sakuli
sakuli copied to clipboard
Sahi should use Sakuli root CA to sign host certificates
Also import via script -> Docker container
will create more work then expected -> move to release 1.1 Entrypoint for code see eaaa95ff1b38b60a272ecdd52e3a97f50d938752, based on http://www.pixelstech.net/article/1408524957-Generate-cetrificate-in-Java----3
Some more usefull informations:
- https://github.com/ConSol/sakuli/issues/53#issuecomment-112488195
- http://sahipro.com/docs/using-sahi/sahi-configuration-basic.html#Configure SSL
- https://github.com/headissue/Sahi/releases
- http://stackoverflow.com/questions/30634658/how-to-create-a-certificate-chain-using-keytool *http://www.pixelstech.net/article/1450354633-Using-keytool-to-create-certificate-chain
- https://dzone.com/articles/tlsssl-terminology-and-basics utm_source=Top%205&utm_medium=email&utm_campaign=top5%202017-05-05
- http://sahipro.com/sahipro-troubleshooting-series-ssl-issues/
- https://dzone.com/articles/ssl-testing-tool?edition=334833&utm_source=Daily%20Digest&utm_medium=email&utm_campaign=Daily%20Digest%202017-11-03
Maybe a additional HTTP proxy can also help:
sakuli/sahi ------ HTTP ----> proxy ------- HTTPS -----> system-under-test
Resources: