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
Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to extend a SSO session inside Visual Studio. Other AWS clients (AWS Toolkit for VS Code, AWS Toolkit for JetBrains, AWS Cli/boto) have a better experience.
Describe the solution you'd like
Make Login with AWS IAM Identity Center equivalent to other AWS Toolkits:
No need to manually copy the user code into the Authorization requested (use VerificationUriComplete instead of VerificationUri)
Thank you for sharing your experience and suggestions around the SSO experience.
We do have plans to update the login flow to avoid copying the user code, as you see in the other clients.
The OIDC client name is currently "decorated" by the AWS SDK for .NET, we will have to investigate opportunities for improving what you see in the login flow there.
The sso scope is something we've more recently realized is different between the Toolkits. We'll look into this as well.
No need to manually copy the user code into the Authorization requested (use VerificationUriComplete instead of VerificationUri)
We have released version 1.47.0.0 of the toolkit that addresses this issue. The AWS Builder Id and IAM Identity Center (SSO) login flow has been improved to confirm that the device code in the Toolkit and browser match.
Is your feature request related to a problem? Please describe.
I'm always frustrated when I need to extend a SSO session inside Visual Studio. Other AWS clients (AWS Toolkit for VS Code, AWS Toolkit for JetBrains, AWS Cli/boto) have a better experience.
Describe the solution you'd like
Make Login with AWS IAM Identity Center equivalent to other AWS Toolkits:
VerificationUriComplete
instead ofVerificationUri
)sso:account:access
for a better reconnection experience aws/aws-toolkit-jetbrains SonoConstants.ktThe text was updated successfully, but these errors were encountered: