Skip to content

Conversation

@wbh1
Copy link

@wbh1 wbh1 commented Dec 12, 2025

Related: #78

As far as I can tell, the cert kwarg1 on an httpx client isn't doing anything. It's deprecated now2, but I wasn't even seeing the expected warning messages. Regardless, when passing an SSLContext to the verify kwarg, it will be used when communicating with Jira.

Confirmed that this works with my own Jira DC instance that uses certificate-based authentication.

Also, for good measure, added a config option to omit HTTP Authorization headers when using cert-based auth.

Footnotes

  1. https://www.python-httpx.org/api/#asyncclient

  2. https://github.com/encode/httpx/blob/ae1b9f66238f75ced3ced5e4485408435de10768/httpx/_config.py#L59-L62

wbh1 added 4 commits December 12, 2025 14:55
As far as I can tell, the `cert` kwarg on an httpx client doesn' nothing. However, you can pass an SSLContext to the `verify` kwarg and it will be used when communicating with Jira.

Confirmed that this works with my own Jira instance that uses certificate-based authentication.

squash me
`rich` crashes out if `account_type` is set to None.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant