The one connect python SDK does not currently allow for self-signed certificates to be authenticated when creating a new client, these will always fail.
Use cases
Self-signed certificates are inexpensive (free) and suitable for use in non-public facing applications.
Proposed solution
Supporting optional self-signed certificates through minor modifications to client.py.
Summary
The one connect python SDK does not currently allow for self-signed certificates to be authenticated when creating a new client, these will always fail.
Use cases
Self-signed certificates are inexpensive (free) and suitable for use in non-public facing applications.
Proposed solution
Supporting optional self-signed certificates through minor modifications to client.py.
Is there a workaround to accomplish this today?
Not using python.
References & Prior Work