Skip to content
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

AWS explorer doesn't reflect the refreshed security token credentials via AWSCLI until I close and re-open the VS #348

Closed
AshokAndani opened this issue Jul 17, 2023 · 7 comments
Labels
bug We can reproduce the issue and confirmed it is a bug. closed-for-staleness Issue closed due to staleness. needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days

Comments

@AshokAndani
Copy link

Refreshed security token credentials via AWSCLI will not reflect in visual studio until I close and re-open the visual studio.

  • security credentials are expired
  1. refresh the security credentials from AWS cli command prompt
  2. open AWS Explorer in VS2022
  3. ERROR: The Security Token included in the request is Expired.
  4. close and re-open the VS and then navigate to AWS Explorer
  5. now it is able to retrieve the information of my account.....
    Screenshot 2023-07-17 084304
@AshokAndani AshokAndani added the bug We can reproduce the issue and confirmed it is a bug. label Jul 17, 2023
@floralph
Copy link
Contributor

Hi, thank you for bringing this issue to our attention. Please provide details for this profile from your ~/.aws/config file (redact any confidential information if needed) and any pertinent messages in the toolkit logs. To access the toolkit logs, click Extensions / AWS Toolkit / View Toolkit Logs. If the issue just occurred, you will typically find it towards the end of the last log (filenames are timestamped) in the logs folder.

@shruti0085 shruti0085 added the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label Aug 1, 2023
@github-actions
Copy link

This issue is missing required information and will be closed in 7 days. To keep the issue open, leave a comment.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 7 days unless further comments are made. label Aug 17, 2023
@AshokAndani
Copy link
Author

as toolkit logs are having lot of confidential information traces hence cannot provide them
here is the config file:
image

@github-actions github-actions bot removed closing-soon This issue will automatically close in 7 days unless further comments are made. needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days labels Aug 18, 2023
@floralph
Copy link
Contributor

Can you also redact and post the contents of the ~/.aws/credentials file that are pertinent to the profile in question? The posted contents of the config file alone are insufficient to be used as a credential. It's unclear how you have your credential that isn't working properly defined.

@floralph floralph added the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label Aug 29, 2023
@AshokAndani
Copy link
Author

here is the /credentials file details
image

but I would request to read the steps mentioned above again...
all the aws stuffs seems fine
I'm guessing Visual Studio is caching the creds hence it is not able to load the new refreshed creds after previous creds expiry until I close and re-open Visual Studio...

@github-actions github-actions bot removed the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label Sep 2, 2023
@shruti0085
Copy link
Contributor

Hello @AshokAndani, a couple questions:

  • Can you confirm if you are using the latest version of the toolkit 1.43.0.0?
  • Instead of closing VS, what happens if you hit "Retry" (as seen in your screenshot) after you have refreshed session token using the CLI? Does switching between credentials selected lead to the same failed connection state?

@awschristou awschristou added the needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days label May 3, 2024
Copy link

github-actions bot commented May 4, 2024

This issue is missing required information and will be closed in 7 days. To keep the issue open, leave a comment.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 7 days unless further comments are made. label May 4, 2024
@github-actions github-actions bot added closed-for-staleness Issue closed due to staleness. and removed closing-soon This issue will automatically close in 7 days unless further comments are made. labels May 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug. closed-for-staleness Issue closed due to staleness. needs-response Waiting on additional info and feedback. Will move to `closing-soon` in 30 days
Projects
None yet
Development

No branches or pull requests

4 participants