SignatureService

SignatureService is what only people sign of themselves: who a user’s keys are and who a team’s. members are. A host holds every workspace’s access to these (internal/roster), so a control. plane that is taken can say neither which keys are somebody’s nor who is in a team. A. workspace’s access is signed through WorkspaceService.SetOwnerWord. The control plane proposes each document from what it holds - a key registered, a member added -. and keeps what was signed; it signs nothing. A client shows a person what they are signing and. signs it with a key of theirs: spin sign, with the keys ssh-agent holds, or the terminal’s. page, with a passkey.

ListPendingSignatures

POST /spin.v1.SignatureService/ListPendingSignatures

What the caller is asked to sign: their keyring when their keys changed, and the roster of each team they own when its members changed.

Request

No fields: {}.

Response

Field	Type	What it is
pending	list of PendingSignature

StartKeyringAnew

POST /spin.v1.SignatureService/StartKeyringAnew

Start the caller’s keyring anew: for a person who lost every key its newest version lists. The next keyring proposed lists the keys they registered since and is signed with one of them. Every workspace they own and every team that names them knows the old keyring, not the new one: their workspaces are recovered by cloning a snapshot of each into a new one, and a team’s owner signs them in again.

Request

No fields: {}.

Response

No fields: {}.

SubmitSignature

POST /spin.v1.SignatureService/SubmitSignature

Take a document a person signed: refused unless it is the one proposed, signed by a key that may sign it.

Request

Field	Type	What it is
kind	SignatureKind
subjectId	string
signed	SignedDocument

Response

No fields: {}.