Skip to content

[Hold][WIP] Workflow Endpoint: how to encrypt secrets #670

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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

Paul-Cornell
Copy link
Collaborator

@Paul-Cornell Paul-Cornell commented Jun 23, 2025

Work in progress. Still waiting for renamed "retrieve" endpoint, and certificate signing.

For now, see:

Copy link
Contributor

@awalker4 awalker4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added some comments! I can add a commit to this branch to update the code samples once the new certificate flow is ready. Some other thoughts:

  • I think the pattern of showing redacted on the encrypted text is a bit noisy. It's instructive to show the ---BEGIN PUBLIC KEY--- headers and such, but the other text will always be garbled nonsense, so there's nothing to "hide". Maybe just ellipses?
{
    "encrypted_aes_key": "x3+......9zD",
    "aes_iv": "k2N......g==",
    "encrypted_value": "gM1......A2m",
    "type": "rsa_aes"
}

@awalker4
Copy link
Contributor

awalker4 commented Jul 12, 2025

See this notebook for an updated flow once https://github.com/Unstructured-IO/platform-api/pull/544 is merged. The response from GET /users/secrets/encryption-certificate can be passed directly into the encrypt function that is now copied into the SDK. The result from this can likewise go straight to the store_secret function.

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.

2 participants