Account page: sign in again from the two-factor step when the sign-in is too old

Abierto
#3,445 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start with admin/src/FluentCMS.Admin/Account/AccountTwoFactor.razor and trace how it handles FCMS3065 and displays Account.TwoFactor.SignInAgainFirst. Then follow the hosted-page authorize flow and account-page return handling to see where prompt=login and resuming enrolment belong. Done means the action returns to the two-factor step with a fresh token, enrolment succeeds, and component and end-to-end tests cover the flow.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:admin type:feature

Problem

Since #3372 (#3444), POST /me/two-factor/enrol and POST /me/two-factor/verify need a token whose sign-in on the hosted pages is at most ten minutes old; an older one is refused with FCMS3065 (403). The account page (admin/src/FluentCMS.Admin/Account/AccountTwoFactor.razor) now shows a message that says to sign in again (Account.TwoFactor.SignInAgainFirst), and the user has to sign out and in by hand and find the page again.

Proposal

On FCMS3065, offer to sign in again from the page: an authorize request with prompt=login that comes back to the account page, where the enrolment goes on with the new token.

Acceptance

  • From the message, one action signs the user in again and returns to the two-factor step of the account page
  • An enrolment that follows within the window succeeds, with a component test and an end-to-end case

For workstation A. Follows #3372 and #3444, which made only the smallest change under admin/.

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.