0.10.6: Sync sign-in comes back through 127.0.0.1 #37

2026-11-08T10:05:12-08:00

root-at-skic commented

2026-11-08 10:05:12 -08:00

Sign-in hung at "signing in … in the browser": browsers open vscode:// links only after a click, and with a live Keycloak session nothing was clicked.

Desktop: a one-off listener on 127.0.0.1 receives the browser's way back, then closes.
Remote and web editors keep the vscode:// URI handler.

Checks: typecheck, unit 94/94, integration 29/29. The extension's auth code run against the live gondor server with a temporary Keycloak user: first sign-in with the login form, second while already logged in (no click), then list, share, invite, token refresh.

Sign-in hung at "signing in … in the browser": browsers open vscode:// links only after a click, and with a live Keycloak session nothing was clicked. - Desktop: a one-off listener on 127.0.0.1 receives the browser's way back, then closes. - Remote and web editors keep the vscode:// URI handler. Checks: typecheck, unit 94/94, integration 29/29. The extension's auth code run against the live gondor server with a temporary Keycloak user: first sign-in with the login form, second while already logged in (no click), then list, share, invite, token refresh.

root-at-skic added 1 commit 2026-11-08 10:05:12 -08:00

0.10.6: Sync sign-in comes back through 127.0.0.1 95c6e60199

Browsers open a vscode:// link only after a click on the page. With a live
identity provider session the sign-in ran without one, so the editor kept
waiting. On the desktop the browser now returns to a one-off listener on
127.0.0.1; remote and web editors keep the URI handler.

root-at-skic merged commit 885977c4aa into main

2026-11-08 10:06:32 -08:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: vscode-extensions/archify-vscode-ext#37