A Fabric Connect token whose user was dropped answers 403 until a reload

Abierto
#1,981 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
56/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start with src/integrations/api/retryExpiredOperationToken.ts and trace how the interceptor handles 401 responses and re-mints a Fabric Connect token. Check how operation errors expose USER_HAS_NO_PERMS and the token user's name; the issue says this specific 403 should trigger one recovery attempt. Done means this case recovers once while unrelated 403 responses do not, and the affected recovery behavior is covered by a test.

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

Descripción

Studio gets stuck when the user behind its Fabric Connect token is deleted:

  • Studio recovers a direct Fabric Connect token only on a 401 (src/integrations/api/retryExpiredOperationToken.ts:19).
  • The in-cluster guard skips re-establishing a connection that is already resolved (checkClusterInstanceAuthenticationBeforeLoad, the checkForFabricConnect && !hasResolvedFabricConnect branch).
  • Harper resolves a still-valid JWT for a dropped user to a principal with no role (harper v5.3.2 security/user.ts:576-581, 518-526).
  • Every operation then answers 403 OP_AUTH_PERMS_ERROR, with unauthorized_access: ["User <name> has no role or permissions..."] (utility/operation_authorization.ts:765), until a reload mints a new token.

#1979 closes the Finish Setup route into this state. Dropping the Fabric Connect principal any other way still reaches it, for example from the Users page or from another client. Fabric Connect resolves to Harper's first super user.

Fix idea: in the token-recovery interceptor, treat that specific 403 like an expired token and re-mint once. The specific 403 is USER_HAS_NO_PERMS naming the token's own user.

Found while root-causing #1979.

🤖 Generated by Anthropic Claude Code (Claude Opus 5.5); posted via @dawsontoth.

Lenguaje dominante
TypeScript
Estrellas
5
Forks
4
Merge medio
2 d 13 h
PR fusionados (30 d)
60

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 HarperFast/studio

Todos los issues de HarperFast/studio

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.