Decrypting Data in a Privileged Context
The POST https://<base_url>/privilegedunwrap API returns the DEK that was wrapped using the wrap API without checking the original document or file ACL. Previously known as ‘TakeoutUnwrap. It will be used to decrypt data exported (ex. takeout) from Google in a privileged context.
Request Parameters
| Parameter | Type | Description |
|---|---|---|
| resource_name | string | Unique identifier for the object. It must match the resource_name that was used to wrap the key. |
| authentication | string | A JWT issued by a third party asserting who the user is, or issued by another key service. |
| reason | string | Additional information about the operation. |
| wrapped_key | string | The base64 binary object returned by the wrap call. |
Example Request
{
resource_name: <resource_name>,
authentication: <Authn-JWT>,
reason: "",
wrapped_key: "eyJ3cmFwcGVkX2tleSI6IkozSnZCTEdVOFlWeWlocGpsWXpyd..."
}
Example Response
{
key: "eyJ3cmFwcGVkX2tleSI6IkozSnZCTEdVOFlWeWlocGpsWXpyd=",
perimeter_id: ""
}
Response Codes
| Response Code | Description |
|---|---|
| 2xx | Success |
| 4xx | Client errors |
Refer to HTTP status codes for details.
