Repository navigation
Support to directly pass the certificate as string/binary to Relay Proxy #266
Description
Is your feature request related to a problem? Please describe.
There is no support to pass the certificate as a string directly while using the Relay Proxy. We can only pass the certificate file path. In Go library, though, we can directly pass the certificate key or use the file path option while using the Relay Proxy.
Description in the code which requires us to pass the path to the certificate file
Method from the Go SDK which allows us to pass the certificate as a bytes array
Describe the solution you'd like
Is there a plan to add the support to pass the certificate as a string/binary date while using the Relay Proxy in Python SDK? It looks like this support can be added by upgrading the urllib3 library version to >=2.0.0.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context about the feature request here.
Activity
keelerm84 commentedon Feb 7, 2024
Thank you for bringing this issue to our attention.
I do think this is something we can support in the next major release (since the version change constitutes a breaking change). However, I cannot give a timeline on when that might be.
I have filed this request in our internal tracker as sc-232759. I will update you on this issue once we have added the requested support.
Again, thank you for letting us know about this request!
ujayant commentedon Aug 26, 2024
@keelerm84 Do you have any further updates on this request?
keelerm84 commentedon Aug 30, 2024
No, I don't have an update on this yet. As I had mentioned before, this would require a breaking change. We strive to limit those unless absolutely necessary, and typically only when the team has available capacity to tackle some of the other larger concerns.
However, I will work to make sure this is done during that next change cycle.
trajuram commentedon Nov 18, 2025
HI @keelerm84 , do you have any update on this request ?
keelerm84 commentedon Nov 18, 2025
I'm sorry @trajuram but I do not have any updates on this yet. I do still have this mark as work to be done when we do our next breaking release, so I haven't forgotten about this. It's just priorities keep preventing us from moving forward with a breaking release.
However, we have been doing a lot of work on this repo lately to support the upcoming data-saving mode and so I am hopeful a major version change will be in the somewhat near future, and we can address this then.
trajuram commentedon Nov 18, 2025
Thanks @keelerm84 , please let us know when we can expect this tentatively ?
keelerm84 commentedon Nov 26, 2025
@trajuram there is so much that is subject to change, that this is just a shot in the dark. But I would guess EOQ1, mid Q2?