You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: support implicit OAuth in VS Code remote environments (#285)
* docs: remove developer preview banner and disclaimer
Remove the "Developer Preview" note and disclaimer from the CLI README,
the preview banner from the docs site theme, and all associated CSS.
* feat: support implicit OAuth in VS Code remote environments (Codespaces)
Add openBrowser and redirectUri options to ImplicitOAuthConfig,
AuthCredentials, and CreateOAuthOptions so callers can customize the
browser opener and redirect URI for implicit auth flows.
The VS Code extension now uses vscode.env.openExternal (opens browser
on the client) and vscode.env.asExternalUri (resolves localhost to the
Codespaces forwarded port URL) so implicit OAuth works in remote
environments where the `open` package cannot reach the user's browser.
* fix: thread openBrowser/redirectUri through B2CInstance path
The content tree, webdav tree, and log tailing features use
configProvider.getInstance() which creates a B2CInstance with its own
internal auth resolution. Thread redirectUri and openBrowser through
OAuthAuthConfig, AuthConfig, createInstanceFromConfig, and
createB2CInstance so these features also use vscode.env.openExternal
in remote environments.
Add `openBrowser` and `redirectUri` options to OAuth strategy creation, allowing callers to customize how the browser is opened and which redirect URI is used during implicit auth. The VS Code extension now uses `vscode.env.openExternal` and `vscode.env.asExternalUri` so implicit OAuth works in Codespaces and other remote environments.
0 commit comments