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

Ouverte
#3,442 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
68/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
csharp

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
C#
Étoiles
567
Forks
107
Merge moyen
1 h 19 min
PR mergées (30 j)
353

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fluentcms/FluentCMS

Toutes les issues de fluentcms/FluentCMS

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.