diff --git a/doc/changes/changes_2.6.0.md b/doc/changes/changes_2.6.0.md
index dbc5013..ec0282d 100644
--- a/doc/changes/changes_2.6.0.md
+++ b/doc/changes/changes_2.6.0.md
@@ -4,7 +4,7 @@
 
 This release changes the strategy for deleting a SaaS database instance, as required by the changed behavior of the actual SaaS backend.
 
-Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and message `Operation.*not allowed.*cluster.*not.*in.*proper state` SAPIPY now retries deleting the SaaS instance for max. 5 minutes.
+Before, SAPIPY used only a fixed waiting time. In case of HTTP responses with status code 400 and their messages containing the text "cluster is not in a proper state" SAPIPY now retries deleting the SaaS instance for max. 30 minutes.
 
 ## Bugfixes
 
diff --git a/doc/changes/unreleased.md b/doc/changes/unreleased.md
index 79e701b..8e31d73 100644
--- a/doc/changes/unreleased.md
+++ b/doc/changes/unreleased.md
@@ -1 +1,9 @@
 # Unreleased
+
+## Summary
+
+tbd.
+
+## Refactorings
+
+* #128: Explicitly configured validation of SaaS SSL certificates in pyexasol connection
diff --git a/test/integration/connection_test.py b/test/integration/connection_test.py
index 4cbcb53..e55cf84 100644
--- a/test/integration/connection_test.py
+++ b/test/integration/connection_test.py
@@ -6,7 +6,7 @@
 
 from exasol.saas.client.api_access import get_connection_params
 
-SSL_OPTIONS = {"websocket_sslopt": {"cert_reqs": ssl.CERT_NONE}}
+SSL_OPTIONS = {"websocket_sslopt": {"cert_reqs": ssl.CERT_REQUIRED}}
 
 
 @pytest.fixture