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

Offen
  • Stimmt etwas nicht?
#2,896 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
18/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
git, macos, nodejs, typescript
Bereich
authentication, devtools

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Java
Sterne
10.7k
Forks
1.5k
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/copilot-sdk

Alle Issues in github/copilot-sdk

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.