SDK 1.0.26+ breaks Entra MCP sign-in unless the host registers its own Entra app (undocumented breaking change)

Ouverte
  • Quelque chose ne va pas ?
#2,896 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
18/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
git, macos, nodejs, typescript
Domaine
authentication, devtools

Piste de recherche

The report centres on the CopilotClientOptions.entra option and EntraAuthConfig in the SDK's types.d.ts, plus whatever code handles Entra sign-in for MCP servers. Start by reading how the runtime's built-in public client is replaced by a required host client ID between SDK 1.0.24 and 1.0.26. Done means a clear decision on whether built-in sign-in is restored or the change is documented as breaking, with a note in the release notes.

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

Description

What happened

Since @github/copilot-sdk 1.0.26 (runtime 1.0.103+), signing in to an MCP server protected by Microsoft Entra ID fails in an SDK host with:

Microsoft Entra authentication requires the host to configure an Entra client ID

The same servers signed in fine with SDK 1.0.24 (runtime 1.0.101). The runtime handled the Entra sign-in itself with a built-in public client, the same way the Copilot CLI still does today.

The release notes for v1.0.25 to v1.0.28 don't mention this. The only trace is the new CopilotClientOptions.entra?: EntraAuthConfig in types.d.ts, described as "Required for built-in Entra sign-in and token renewal" and marked @experimental. Updating the SDK silently broke Entra MCP servers for every user of my app.

Why a host client ID is not a fix

An SDK app is used across many organisations' tenants. Requiring the app's own Entra registration means every organisation must consent to that app before its users can reach their own MCP servers. That doesn't work in practice, and Copilot CLI users don't need it.

What I'm asking

Please undo this breaking change: restore the built-in Entra sign-in for SDK hosts as it worked in 1.0.24, the way the Copilot CLI still signs in, so the SDK is usable with Entra-protected MCP servers again without the host registering its own app.

If the change has to stay, please at least list it as a breaking change in the release notes.

Versions
  • Works: @github/copilot-sdk 1.0.24 (runtime 1.0.101).
  • Fails: @github/copilot-sdk 1.0.26 and later (runtime 1.0.103 and later), seen on macOS.
Langage dominant
Java
Étoiles
10.7k
Forks
1.5k
Aucune PR mergée en 30 j

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 github/copilot-sdk

Toutes les issues de github/copilot-sdk

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

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