SSL Error, Handshake about sakuli HOT 6 CLOSED

Did you run your Sakuli tests after you imported the self-signed certificates via Sahi dashboard?
If not, did you add the generated certificates to your Docker image when re-running the tests?

from sakuli.

The script i wrote should generate a certificate on it's own and present the data in a mapped volume,
the problem is when it runs, it uses sakuli and then there is no "add exception" button in firefox.
If i do the same steps, but just with sahi (dashboard) this option is present.
It seems like the handshake negoation fails when sakuli is used as starter and i don't find any solution to debug this.

So there are no certificates available at this point to include them.

from sakuli.

ok seems like sakuli isn't able to generate any certificates using sahi.
after generating a certificate with sahi, sakuli just works fine.

i wasn't aware of that, maybe someone should mention this in the documentation and
sakuli should be able, thru sahi, to generate certificates too.

from sakuli.

Sakuli itself does not handle connections, that's all handled via Sahi proxy. It's explained in the Sakuli docs how to handle certificates via Sahi. Alternatively, you could prepend your test with a helper to accept certificates via test actions.

from sakuli.

@s1hofmann exactly that's the point, since sahi handles the the connections you would guess that it should be able to generate certificates, even if it's called by the suite sakuli.

i mean't with the part in the documentation that it is not clear that sakuli as suite is not able to generate a ssl certificate, i think this should be mentioned explicitly.

thanks for your time

from sakuli.

Thanks for your feedback! We're reliant on user feedback in order to improve our docs, so things like this will be clarified more!

from sakuli.