Skip to content

feat: aws native multi session - #618

Open
keval6b wants to merge 2 commits into
Noovolari:masterfrom
keval6b:feat/aws-native-multi-session
Open

feat: aws native multi session#618
keval6b wants to merge 2 commits into
Noovolari:masterfrom
keval6b:feat/aws-native-multi-session

Conversation

@keval6b

@keval6b keval6b commented May 2, 2026

Copy link
Copy Markdown

This has been bugging me for a while. Written with AI assistance. Manually tested as thoroughly as I can.

Changelog

  • Removed the Leapp Browser Extension dependency for AWS multi-console support
  • AWS web console sessions now open using direct federation login URLs with AWS native multi-session
  • Removed the WebSocket server that ran on port 8095
  • Replaced the "Enable Multi-Console Extension" toggle in Options with an informational panel that explains how to enable AWS native multi-session

Bugfixes

N/A

Enhancements

  • AWS multi-console support no longer needs a separate browser extension (previously via Firefox Add-ons and a CDN hosted Chromium zip). AWS supports up to 5 simultaneous console identities per browser using per account subdomains. Users enable it once per browser by choosing "Turn on multi-session" in the AWS console account menu.
  • Simplified the web console code path. All entry points (contextual menu, bottom bar, session card Cmd/Ctrl click) now use one direct federation call. There is no extension branching.
  • Removed extensionEnabled from the persisted workspace settings schema. Existing workspace files with the old _extensionEnabled field will still load. The field is ignored.

Notes

  • AWS multi-session is an opt in setting, not automatic. Users must enable it once per browser from the account menu in the AWS Management Console (console.aws.amazon.com). If users do not enable it, opening a second session will overwrite the first. This is normal AWS browser behavior, not a Leapp issue.
  • The 5 session browser limit is handled by AWS. Leapp does not track active browser sessions and does not manage this limit.
  • The browser extension (leapp-multi-console-extension) is not removed. It is still available on Firefox Add-ons and the CDN for users who want it. Leapp just will not connect to it anymore.

keval6b added 2 commits May 2, 2026 11:02
Remove the ExtensionWebsocketService and its WebSocket server (port 8095),
the extensionEnabled setting, and all conditional extension code paths.
AWS console sessions now open via direct federation login URLs, with AWS
handling per-session subdomain isolation natively when the user has opted
in to multi-session via the AWS console account menu.

Also drop the legacy OAuth logout-then-redirect wrapper that caused 400
errors; federation login URLs are now opened directly.
On the first web console open after updating, display an 8-second
info toast prompting the user to enable AWS native multi-session in
their browser account menu. Persisted in workspace settings so it
only shows once.
@keval6b keval6b closed this May 2, 2026
@keval6b
keval6b deleted the feat/aws-native-multi-session branch May 2, 2026 22:21
@keval6b
keval6b restored the feat/aws-native-multi-session branch May 5, 2026 21:15
@keval6b keval6b reopened this May 5, 2026
@sonarqubecloud

sonarqubecloud Bot commented May 5, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant