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
