github / github/vscode-github-actions

GitHub Enterprise sign-in fails with "No auth flow succeeded" using OAuth and PAT on VPN

Abierto
#488 1 comentario 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
TypeScript
Estrellas
660
Forks
213
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

🐛 Describe the bug
VS Code fails to authenticate with our GitHub Enterprise server (https://git.cedacrigroup.it) via any supported auth flow.
After attempting both OAuth and Personal Access Token (PAT), the error Sign in failed: Error: No auth flow succeeded is always shown.

🔁 To Reproduce
Steps to reproduce the behavior:
Connected to company VPN
Open VS Code (latest version)

Sign in to GitHub Enterprise:
OAuth → browser opens, but fails to complete flow
Device code → hangs or fails
PAT → accepted, then "No auth flow succeeded" error
VS Code never completes login

✅ Expected behavior
Login to GitHub Enterprise (git.cedacrigroup.it) should complete either via OAuth, device code, or PAT.
The GitHub Pull Requests and Issues extension should be able to authenticate properly.

📷 Screenshots
OAuth failure:
Sign in failed: Error: No auth flow succeeded.
Image

PAT failure:
Same message after entering token.

Extension prompt appears but does not finish.

📦 Extension Version
github.vscode-pull-request-github: 0.112.0
ms-vscode.azure-repos: 0.40.0
github.vscode-github-actions:
0.27.2

VS Code: 1.101.2 (user setup)
Image

OS: Windows 11
VPN: Yes (corporate)

📎 Additional context
The GitHub Enterprise server is reachable in browser (https://git.cedacrigroup.it)
SSO might be enabled on the enterprise server
Tried setting github.gitAuthenticationHosts and github.enterpriseServer in settings.json
Also attempted to manually set github-enterprise.uri

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.