connect-sdk-python icon indicating copy to clipboard operation
connect-sdk-python copied to clipboard

Python SDK for 1Password Connect

Results 28 connect-sdk-python issues
Sort by recently updated
recently updated
newest added

Add support for generator recipies. This was generated using a newer version of the OpenAPI tools, I think, because it looks slightly different. It does however work using the simple...

Starting with Connect 1.5.4, the `file_id` in the item representation is no longer the file ID, but the wrapping field's ID. (see the difference between the `content_path`'s last token and...

bug

### Summary I have existing CLI scripts which list secrets as k:v pairs by tag, using the v1 version of `op`. I'd like to be able to do this with...

enhancement
tracked

### Your environment SDK Version: 1.2.0 - installed via pip install onepasswordconnectsdk Connect Server Version: OS: Ubuntu 20.04 Python Version: 3.8.10 ## What happened? Using load_dict against a key with...

bug
tracked

### Your environment SDK Version: v1.1.0 Connect Server Version: Docker image `1password/connect-sync@sha256:ea4ee8de21de22edcf35b4218fe4ce0c18f3806b7e3b259e5a7e0f98065fed45`, created around 2021-05-20 OS: Ubuntu 20.04 Python Version: 3.8 ## What happened? We created a default password item...

bug
tracked

Hi, Playing around with Secrets Automation and trying to use the Python SDK for this. I've deployed the Connect server via the docker-compose file that is on the 1password website...

For some use cases, for instance, when there's a VPN between the computer running the client and the 1password servers the default timeout may not be enough. In those cases...

Support added for self-signed certificates. This addresses issue #95. I have tested and confirmed working with the synchronous client.

### Your environment SDK Version: N/A Connect Server Version: N/A OS: N/A Python Version: N/A ## What happened? I am admittedly unsure what category to file this under, but I...

bug

The example for onepasswordconnectsdk.load_dict() in USAGE.md was inaccurate and would result in errors. This has now been corrected and will now actually work. This addresses #97.