Vault unlock

Tag 12: the server relays an ask of the container that unlocks a key of the vault the client holds; the client answers with exactly one channel response, ok or an error, which the server relays to the container.

The server opens this channel when the container’s proxy sends a vault ask on /requests that unlocks a key. The ask is relayed verbatim; the client’s one answer is relayed back.

• The request. The tag byte 12 followed by the ask in the form the proxy’s /vault/unlock/{channel} page defines. Request states its form.
• The response. Exactly one channel response and the channel response finish. Response states the sequence.
• The conduit. The server relays the one channel response to the proxy’s /vault/unlock/{channel} as one message and closes that connection. The server does not read the key or the value, and does not send the ask twice.
• The namespace. The server determines which vault the key belongs to; the ask names no vault.