Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[UC] Silent Authentication #41

Open
jeswr opened this issue Dec 17, 2024 · 0 comments
Open

[UC] Silent Authentication #41

jeswr opened this issue Dec 17, 2024 · 0 comments
Labels
triage Issues needing triage usecase LWS Use Case

Comments

@jeswr
Copy link
Member

jeswr commented Dec 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issues needing triage usecase LWS Use Case
Projects
None yet
Development

No branches or pull requests

1 participant