Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for self-signed certificates #95

Open
kwilsonmg opened this issue Mar 5, 2024 · 1 comment
Open

Add support for self-signed certificates #95

kwilsonmg opened this issue Mar 5, 2024 · 1 comment

Comments

@kwilsonmg
Copy link

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

@kwilsonmg
Copy link
Author

I have a PR incoming implementing this.

kwilsonmg added a commit to kwilsonmg/connect-sdk-python that referenced this issue Mar 5, 2024
Support added for self-signed certificates. This addresses issue 1Password#95
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

No branches or pull requests

1 participant