A duplicated admin tab signs out its opener about an hour later

Abierto
#3,280 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
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Read admin/src/FluentCMS.Admin/Authentication/AdminSession.cs:89-105 and the TwoTabsTests case that covers refreshes within the 30-second reuse leeway. Trace how session restore and refresh-token redemption interact across tabs, then add an end-to-end case for an opener and duplicate remaining signed in past an hour. Done means the test passes and a copied session drops its inherited refresh token before silently signing in through authorize.

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

Descripción

area:admin type:bug

Problem

A duplicated admin tab starts with the opener's sessionStorage and redeems the stored refresh token (admin/src/FluentCMS.Admin/Authentication/AdminSession.cs:89-105), while the opener still holds the same token in memory. At the opener's next refresh, well past the server's 30-second reuse leeway, it presents a redeemed token, gets invalid_grant and is sent to sign in. TwoTabsTests covers only refreshes within the leeway.

Proposal

Detect a copied session at restore (a per-tab id answered over BroadcastChannel); a copy drops the inherited refresh token and signs in silently through authorize.

Acceptance

  • An opener and its duplicate both stay signed in past an hour
  • An end-to-end case covers it

Found in the code review of 17 Nov 2026 (B9).

Lenguaje dominante
C#
Estrellas
569
Forks
107
Merge medio
2 h 49 min
PR fusionados (30 d)
397

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.