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

KeyAccessObject encryptedMetadata required? #47

Open
arkavo-com opened this issue Nov 3, 2024 · 0 comments
Open

KeyAccessObject encryptedMetadata required? #47

arkavo-com opened this issue Nov 3, 2024 · 0 comments

Comments

@arkavo-com
Copy link

Is encryptedMetadata required? spec and impl differ

Specification:

|`encryptedMetadata`|String|Metadata associated with the TDF, and the request. The contents of the metadata are freeform, and are used to pass information from the client, and any plugins that may be in use by the KAS. The metadata stored here should not be used for primary access decisions. <p>Note: `encryptedMetadata` is stored as [a base64-encoded string](https://en.wikipedia.org/wiki/Base64#Base64_table). One example of the metadata, decoded and decrypted, could be, depending on specific needs:<p><code>{authHeader:"sd9f8dfkjhwkej8sdfj",connectOptions:{url:'http://localhost:4010'}}</code>|Yes|

Implementation:
https://github.com/opentdf/platform/blob/aeb898b38ce01de92ea7569010d16d67c1339902/service/kas/access/keyaccess.go#L4

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