Description (User Story)
This is the user journey for credentials that have short expiration times. One goal of a PEMC is that the issuer is not notified when the credential is used. One way that the mDL standard accomplishes this is to make one part of the license have a short duration and expect that it will be updated "frequently".
Narrative
What happens during the use case.
Anti Use Case
The user journey to be avoided in that the user gets to a place where the credential is checked and it has expired. Two paths are open, neither of them is privacy enhancing.
- The user allows a refresh of the credential at that point which give the issuer information about where the credential was used.
- The user is not allowed to access the desired resources.
Here is an actual user journey that is to be avoided. Holder goes to get a new driver's license at the stipulated interval at a physical license issuing site. The existing physical license has a hole punched in the card indicating that it is no longer useful for the purpose of driving, but is explicitly told that the license is still valid for identification. The holder is also issued a temporary license as an 8 x 11 piece of paper which is placed in the car's glove box. The holder goes to a restaurant which apparently has been shut down for liquor license violation and has been told to "card" every one regardless of their age. The card with a hole in it is rejected by the manager in the restaurant. The problem is that the policy as enunciated by the license issuing authority does not match the policy applied by the restaurant. The holder is rejected by the verifier because the policies are not coordinated.
Actors
| Actor | Role in the use case |
|---|---|
| Alice | |
| Bob | |
| etcetera |
User Stories
| Element | Detail | Notes |
|---|---|---|
| As a, | <description of user> | |
| I want | <functionality> | |
| so that | <benefit> | |
| Acceptance Criteria | ||
| Given | <how things begin> | |
| When | <action taken> | |
| Then | <outcome of taking action> | |
Prerequisites / Assumptions
Use Case Details
Privacy
Data Provided
Data Retained
Diagram
Steps
Primary Use Case
The anticipated normal sequence
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Secondary Use Case(s)
Alternate or variant sequences
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Sequence Diagram
End State
Describe what measures or signifies the end of the case
Success
Markers or metrics that indicate success
Failure
Markers or metrics that indicate failure
References
Champion / Stakeholder
List of the people that created the use case
Related Material
Resources and Links