MCP client redirect URIs: custom schemes shown as a host, and a change of host case never stored

Abierto
#3,442 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
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start in src/FluentCMS.Core/Identity/Oidc/ by reading ClientConsents.HostOf and ClientRegistrationService.IsCurrentAsync, then trace the authorize endpoint’s redirect URI comparison. Add tests for custom-scheme consent display and for a host-case-only configuration change taking effect after the next start without ending consents; done when both behaviors pass.

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

Descripción

area:identity plugin type:bug

Two defects in how redirect URIs of MCP clients are read (src/FluentCMS.Core/Identity/Oidc/), found in the review of #3434. Both are older than it.

  • The consent page shows the authority of a custom-scheme redirect URI as a web host. ClientConsents.HostOf now shows the scheme for com.example.app:/cb, but myapp://callback/x still shows callback as if it were a host.
  • A configured redirect URI changed only in the case of its host is never stored. ClientRegistrationService.IsCurrentAsync treats it as current, so the stored string keeps the old spelling. If the authorize endpoint compares the stored string exactly, a client that sends the URI as it is now configured is refused. Check which comparison the authorize endpoint makes, then store the configured spelling or normalize both sides.

Wanted

  • A custom-scheme redirect shown by its scheme, never as a host, with a test.
  • A configured redirect URI that changes only in case works at the authorize endpoint after the next start, with a test, and without ending consents.

Found in the review of #3434. Bundle 26.

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.