You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I want to re-visit a Solid Web page after several days of not being logged in, So that I do not have to re-authenticate.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
The user has logged into the Web Page in the past on the current device and browser
The user has not logged out since the last login
Trigger:
What (user or system) event or action initiates this use case?
User visiting the Web page
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
The user
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Not interrupting user flows with the need to authenticate (this means that the Web page should also not need to redirect to a server-managed page to automatically authenticate without user input).
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
The user visits the webpage and immediately sees that they are logged in
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
NA
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
NA
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
It must be possible to build a Solid applications which can silently authenticate users after a long period of non-interaction.
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
Consider applications like GitHub or Google in which you remain logged in after long periods of inactivity.
The text was updated successfully, but these errors were encountered:
As a user
I want to re-visit a Solid Web page after several days of not being logged in,
So that I do not have to re-authenticate.
Preconditions:
What conditions must be in place or assumed before this use case can begin?
Trigger:
What (user or system) event or action initiates this use case?
Actors:
Describe the primary actor, and any other relevant actors involved in this use case
Distinction:
What unique challenges or distinguishing factors (like technical issues, user experience needs, workflow integration, etc.) are associated with this use case?
Scenario:
Describe an ideal or happy-case scenario where this use case would play out as intended.
Alternative case(s):
What alternative flows or variations should the system handle for this use case?
NA
Error scenario:
What unexpected issues or errors might arise, and how should the system handle them?
NA
Acceptance Criteria:
What conditions or criteria must be met for this use case to be considered successfully handled? What limitations are acceptable?
It must be possible to build a Solid applications which can silently authenticate users after a long period of non-interaction.
References:
List any relevant resources or examples that could inform this use case, possibly from other domains or solutions.
Consider applications like GitHub or Google in which you remain logged in after long periods of inactivity.
The text was updated successfully, but these errors were encountered: