chore: use new not_valid_after_utc cert field (#261)

GoogleCloudPlatform · Feb 28, 2024 · ce5f4e8 · ce5f4e8
1 parent bb693e6
commit ce5f4e8
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/google/cloud/alloydb/connector/refresh.py b/google/cloud/alloydb/connector/refresh.py
@@ -96,7 +96,7 @@ def __init__(
         ca_cert, cert_chain = certs
         # get expiration from client certificate
         cert_obj = x509.load_pem_x509_certificate(cert_chain[0].encode("UTF-8"))
-        self.expiration = cert_obj.not_valid_after.replace(tzinfo=timezone.utc)
+        self.expiration = cert_obj.not_valid_after_utc
 
         # tmpdir and its contents are automatically deleted after the CA cert
         # and cert chain are loaded into the SSLcontext. The values

diff --git a/setup.py b/setup.py
@@ -22,7 +22,7 @@
 release_status = "Development Status :: 4 - Beta"
 dependencies = [
     "aiohttp",
-    "cryptography>=38.0.3",
+    "cryptography>=42.0.0",
     "requests",
     "google-auth",
     "protobuf",