Skip to content

Error "self signed certificate in certificate chain" or other SSL-related error

When accessing Botium endpoints on servers that don’t have a certificate signed by a globally trusted certification authority, Botium will refuse connection and test cases are failing.

Note

This typically happens when using the Generic HTTP(S)/JSON connector, or a connector derived from it (most custom connectors).

The solution is to tell Botium to ignore SSL specific errors like this.

  1. Open the chatbot connected to the HTTPS endpoint in question

  2. Go to Settings / Environment Settings

  3. Register a new environment variable NODE_TLS_REJECT_UNAUTHORIZED with value 0

  4. Don’t forget to save the changes

Now the errors about self-signed certificates should be ignored by Botium.

Note

You can reach the same by adding this environment variable NODE_TLS_REJECT_UNAUTHORIZED to your docker-compose file or your Kubernetes deployment. In this case, it is in effect globally for all chatbot connectors.

Still SSL Error: DEPTH_ZERO_SELF_SIGNED_CERT or other

In case you receive an additional error about DEPTH_ZERO_SELF_SIGNED_CERT or anything else, you have to tell Botium to ignore these errors as well.

  1. Open the chatbot connected to the HTTPS endpoint in question

  2. Go to Settings / Connector Settings and choose Other (Advanced Settings) in the Connector/Chatbot Technology dropdown (or enable the Advanced Mode switch, depending on your Botium Box version)

  3. Register a new capability SIMPLEREST_STRICT_SSL with type Checkbox and let it disabled

  4. Don’t forget to save the changes

Now basically all SSL problems are ignored by Botium.