Feature Request: Add support for custom Host header and SSL context configuration

Open
#78 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api, backend

Research direction

Locate the Python client initialization methods with_private_key(), with_client_credentials(), and with_access_token(), then trace how they configure requests. Done means callers can provide a custom Host header and SSL context, including for proxy deployments and private certificate authorities; add or update tests where the request configuration is covered.

Written by the indexing model from the issue text.

Description

Description

The current Zitadel Python client initialization methods (with_private_key(), with_client_credentials(), with_access_token()) don't provide parameters to:

  • Set a custom Host in the header for requests
  • Configure a custom SSL context for private/self-signed certificates
    This limitation makes it difficult to use the client in common deployment scenarios, particularly when Zitadel is running behind a proxy with externalSSL=true external domian and and internal container-to-container communication is needed, or when using private Certificate Authorities (e.g., mkcert for development).
Dominant language
Python
Stars
16
Forks
3
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from zitadel/client-python

All issues in zitadel/client-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.