User Story: Undo Share a Credential

Contents

• Context
  • lcw.app User Story Description
  • Recommended Implementation
    • Assumptions
    • Implementation Overview
• Conversation
• Confirmation
  • Deleting a named resource
    • Deleting resource named /space/:spaceUuid/:name
• Implementations
  • wallet-attached-storage-server
  • wasup

Context

This document describes a user story where an end-user Alice decides to 'undo' a previous decision to share a credential.

lcw.app User Story Description

This user story description was an input to this user story:

Alice decides that she no longer wants to share her Verifiable Credential that she previously shared (in user story S2.A).

She goes to the VC's Share screen in LCW, and clicks 'Unshare credential'.

LCW sends a DELETE request to the VC's location on her attached storage instance, which removes the VC from attached storage.

Subsequent GET requests to the URL of that VC will result in an HTTP 404 Not Found response.

Recommended Implementation

Assumptions

1. Alice's LCW App already has an Ed25519 did:key authorized to read/write a Space
2. Alice's LCW App already knows the URI of the result of the previous action of sharing the credential, e.g. /space/:spaceUuid/vc

Implementation Overview

1. Alice requests DELETE /space/:spaceUuid/vc with an HTTP Signature from an authorized key

Conversation

We seek to socialize this user story widely as a core user story for the Wallet Attached Storage protocol.

Plan of conversation:

1. Publish this user story at a final public URL

• Actions
  • bengo: https://github.com/gobengo/wallet.storage/issues/3

2. Solicit feedback from digitalcredentials.mit.edu
3. Incorporate feedback into the user story andd add to change log

If you want to be a part of the conversation, please publish feedback and link to Wallet Attached Storage.

Confirmation

This section describes how to confirm that an implementation has satisfied the user story.

Given

• a user has a digital wallet that supports the Wallet Attached Storage protocol
• the user has a Verifiable Credential (VC) in their wallet that they want to share publicly
• the user has a conformant Wallet Attached Storage server that supports the protocol

when

• the wallet has shared a Verifiable Credential to /space/:spaceUuid/vc as described in User Story: Space Controller Shares a Credential Publicly
• the wallet deletes a resource named /space/:spaceUuid/vc and follows response redirects

then

• the response MUST status MUST be one of 200, 204

Deleting a named resource

Deleting resource named /space/:spaceUuid/:name

DELETE /space/:spaceUuid/:name HTTP/1.1
Authorization: Signature keyId="did:key:{mk}#{mk}"…

Implementations

wallet-attached-storage-server

wallet-attached-storage-server intends to implement this user story.

wasup

@wallet.storage/wasup is a CLI and supports sending DELETE requests as described above like

wasfetch [--identity ~/.ssh/id_ed25519_was_test] <url> -m delete