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

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
git, macos, nodejs, typescript
Área
authentication, devtools

Línea de trabajo

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.

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

Descripción

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.
Lenguaje dominante
Java
Estrellas
10.7k
Forks
1.5k
Sin PR fusionados en 30 d

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

Todos los issues de github/copilot-sdk

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.