Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Static OAuth client loses its SEP-2352 issuer stamp across SDK saves and restarts

Abierto
  • ¿Algo no está bien?
#2,751 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@rajnish-verma-22172 ya está trabajando en esto.

Desde el 21/10/2026.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
authentication, backend

Línea de trabajo

Start in core/auth/providers.ts by tracing clientInformation(), saveClientInformation(), and resolveSdkRegistrationKind; then find the related auth provider tests. Reproduce the sequence in the issue: save a preregistered client, back-stamp { issuer }, and reinitialize with the same static config. Done when the issuer persists across that sequence and no warning fires.

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

Descripción

bug v2

Problem

For a static (preregistered) OAuth client, the SEP-2352 issuer stamp doesn't survive SDK saves and CLI restarts, so the issuer binding is missing and the SDK warns again on every run.

In core/auth/providers.ts:

  • clientInformation() returns the preregistered slot first (issuer-independent).
  • The SDK's back-stamp after discovery goes through saveClientInformation() with { issuer } only. That routes through resolveSdkRegistrationKind into the per-issuer dynamic slot, which the preregistered read never looks at.
  • Re-seeding the static client at init then drops whatever was stamped.

The effect: the binding falls back to the SDK's unbound legacy behaviour, and the warning repeats on every restart. Reported against 2.11.0.

Expected

Once the SDK has stamped the issuer for a preregistered client, the stamp persists with that client and is returned on the next read. Re-seeding the same static client at startup keeps an existing stamp unless the client itself changed.

Notes

  • Cover it with a test: save a preregistered client, SDK back-stamp with { issuer }, re-init with the same static config, then assert the issuer is present and no warning fires.

Priority score

Severity 3, Urgency 3, +1 bug, +1 milestone, Total 8 → Medium.

Lenguaje dominante
TypeScript
Estrellas
11.1k
Forks
1.6k
Merge medio
5 h 29 min
PR fusionados (30 d)
158

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 modelcontextprotocol/inspector

Todos los issues de modelcontextprotocol/inspector

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.