Repository navigation
Honor SSL_CERT_FILE and REQUESTS_CA_BUNDLE for TLS verification - #1034
Closed
SachuJames wants to merge 1 commit into
Closed
SachuJames wants to merge 1 commit into
SachuJames wants to merge 1 commit into
Conversation
Both clients hardcoded the certifi bundle, so custom CA bundles (common behind corporate TLS inspection) were silently ignored. Resolve the CA bundle from SSL_CERT_FILE, then REQUESTS_CA_BUNDLE, falling back to certifi as before.
SachuJames
requested review from
jbonzo,
justinpolygon,
kschoche,
lukeoleson,
mmoghaddam385 and
suever
as code owners
October 12, 2026 12:23
justinpolygon
added a commit
that referenced
this pull request
Oct 16, 2026
Combines the community PRs that change how the REST client builds its urllib3 pool (#968, #1008, #1026, #1033, #1034). - CA bundle: both clients verify TLS with ca_certs if given, then the SSL_CERT_FILE or REQUESTS_CA_BUNDLE environment variable, then certifi (#998). - RESTClient(maxsize=10): connections kept per host. urllib3 defaults to 1, so threaded clients kept opening new TLS connections. - RESTClient(connection_pool_kw=...): other urllib3 pool options, merged over the defaults (#1009). - RESTClient(proxy=...): explicit proxy URL, with credentials from the URL. Proxy environment variables aren't read, so existing traffic doesn't change route. The WebSocket client already uses the system proxy via websockets. Co-authored-by: SACHU JAMES <142034811+SachuJames@users.noreply.github.com> Co-authored-by: Mohd Quamar Tyagi <104281681+Tyagiquamar@users.noreply.github.com> Co-authored-by: jakobovski-arb <201493996+jakobovski-arb@users.noreply.github.com> Co-authored-by: Roman Zydyk <31843161+romanzdk@users.noreply.github.com> Co-authored-by: Kevin Chiu <2712+kevinchiu@users.noreply.github.com>
justinpolygon
added a commit
that referenced
this pull request
Oct 16, 2026
Adds connection options to the clients, combining #968, #1008, #1026, #1033 and #1034 (contributors are credited as co-authors). - **Custom CA:** `ca_certs=` on `RESTClient` and `WebSocketClient`, defaulting to `SSL_CERT_FILE` / `REQUESTS_CA_BUNDLE`, then certifi. Closes #998. - **Pool size:** `RESTClient(maxsize=10)`. urllib3 defaults to 1 connection per host. - **Pool options:** `RESTClient(connection_pool_kw={...})`, merged over the defaults. Closes #1009. - **Proxy:** `RESTClient(proxy="http://user:pass@host:port")`. Proxy env vars aren't read, so nobody's traffic changes route. The README has a new **Network Configuration** section with examples for each case (custom CA, proxy, threads, other pool options). All new parameters are optional and added at the end of the signatures. The one behavior change: if `SSL_CERT_FILE` or `REQUESTS_CA_BUNDLE` points to a file, it's now used instead of certifi (as `requests` and Python do). If it points to a file that doesn't exist, it's skipped with a warning, so a stale value doesn't break anyone. Verified against the live API through a local TLS-inspecting proxy (mitmproxy with auth): REST and WebSocket connect with the proxy's CA (argument or env var) and fail certificate verification without it; wrong proxy credentials get 407. Under 16 threads, `maxsize=10` opened 16 TLS connections vs 57–70 with urllib3's default. --------- Co-authored-by: SACHU JAMES <142034811+SachuJames@users.noreply.github.com> Co-authored-by: Mohd Quamar Tyagi <104281681+Tyagiquamar@users.noreply.github.com> Co-authored-by: jakobovski-arb <201493996+jakobovski-arb@users.noreply.github.com> Co-authored-by: Roman Zydyk <31843161+romanzdk@users.noreply.github.com> Co-authored-by: Kevin Chiu <2712+kevinchiu@users.noreply.github.com>
Collaborator
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Both the REST and websocket clients hardcode
certifi.where()for TLS verification, so settingSSL_CERT_FILEorREQUESTS_CA_BUNDLEhas no effect. Anyone behind a corporate proxy with a custom CA bundle cannot use the SDK.Fixes #998
What changed:
massive/certs.pywithca_bundle_path(): resolvesSSL_CERT_FILEfirst, thenREQUESTS_CA_BUNDLE, falling back tocertifi.where().massive/rest/base.py:PoolManagernow usesca_bundle_path()forca_certs.massive/websocket/__init__.py: extracted the inline SSL context into_ssl_context(), loadingca_bundle_path().Tests:
test_rest/test_ssl.py(7 tests): env precedence, certifi default, and client-level check viaconnection_pool_kw["ca_certs"].test_websocket/test_ssl.py(4 tests): mockedload_verify_locationscaptures the bundle path;ws://builds no context.