Skip to content

feat(auth): add STS credential management #7661

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: feature/flare-mega
Choose a base branch
from

Conversation

yuxianrz
Copy link

@yuxianrz yuxianrz commented Jul 14, 2025

Problem

aws-toolkit-vscode does not currently support assume role by inputing user keys (access key and secret key set) and role argument. To keep it consistent with other toolkit IDEs' implementation and give clients a third option to sign in beside SSO and long-term IAM credentials, this feature should be implemented.

Solution

This is part of #7507 and is built on top of #7659.

  • Add STS credentials options to LanguageClientAuth requests, including update, invalidate, and cache
  • Add STS credentials' role argument input to IAM credentials form to webview
  • Modify clients to support IAM and STS credentials

Meanwhile, we are making changes to language-servers and language-server-runtimes such that authentication for IAM credentials can happen on Flare side.

Tests will work with this version of language-server-runtimes:
https://github.com/liramon1/language-server-runtimes/tree/feature/flare-iam

and this version of language-servers:
https://github.com/liramon1/language-servers/tree/liramon/flare-iam

Please reference these when reviewing our work


  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@yuxianrz yuxianrz requested review from a team as code owners July 14, 2025 18:19
Copy link

  • This pull request implements a feat or fix, so it must include a changelog entry (unless the fix is for an unreleased feature). Review the changelog guidelines.
    • Note: beta or "experiment" features that have active users should announce fixes in the changelog.
    • If this is not a feature or fix, use an appropriate type from the title guidelines. For example, telemetry-only changes should use the telemetry type.

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