End-to-end cases of the admin left out of the first harness

Aperta
#3,213 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

Start with the end-to-end harness from #3149 and the review of #3206, then trace the account page work in #3147 and the IFormDraftStore flow in A2. Add the listed browser cases, including secret redaction checks for authenticator keys and recovery codes. Done means each case is covered and the sensitive account steps are excluded from kept traces.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:admin area:testing type:feature

The end-to-end harness of #3149 covers sign-in, sign-out, a session the server ends, two tabs, the sidebar and the site switch. These browser cases of #3149 and of its first comment are not covered and are tracked here:

  • The form draft is kept across an expired session and restored after the new sign-in (waits for a page that uses IFormDraftStore, in A2). (#3242)
  • Sign-out asks first when a form has unsaved changes (same). (#3246)
  • Back after sign-in does not replay the callback; a failed or reloaded callback shows the error state and a way to start again.
  • A logout the user does not confirm on the hosted page leaves the admin signed in.
  • sessionStorage blocked: the admin says so instead of looping.
  • A user who must change its password, and one whose role requires two-factor, are sent through the hosted pages and come back.
  • An endpoint that hangs: the admin's bounded waits end with a message.
  • Two tabs past the server's 30-second reuse leeway of a refresh token.
  • The account page (#3147): sessions listed and one ended, two-factor enrolment with a code computed from the shown key, recovery codes shown once, disable; an external login removed; the password change link and its return. Before these are written, the trace handling must cover secrets that no pattern matches: the authenticator key and the recovery codes appear in screenshots and in snapshot text, so the run's literal values are checked and screenshots of those steps are left out of a kept trace.

From the review of #3206.

Lingua principale
C#
Stelle
567
Fork
107
Merge medio
1h 19m
PR unite (30g)
353

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fluentcms/FluentCMS

Tutte le issue di fluentcms/FluentCMS

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.