-
Notifications
You must be signed in to change notification settings - Fork 474
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
Add credential_process support #317
Comments
Thank you for the request @tahoward , the Toolkit for VS Code is developed in Typescript, currently using V2 of the AWS SDK for Javascript. The SDK does not appear to support |
@tahoward I had a chat with someone from the JS SDK team. It sounds like |
@awschristou Thanks for looking into it! |
Just wanted to ping that |
If I understand correctly, all that we need to do is bump our dependency on |
That's my understanding as well, though the current requirement in |
Took a quick look and we'll need to refactor our credential handling--right now, we're handling credentials rather than profiles. This change should be relatively quick once we move to profile handling. |
Add dependency on sinon to write tests
@tahoward @MetricMike A change that introduces support for credential_process has just been merged to the |
Today version 1.1.0 of the Toolkit has been released, which includes credential_process support. |
Is your feature request related to a problem? Please describe.
For Enterprises using SAML based authentication against AWS through services like Okta there is no seamless fully integrated way to assume a role in AWS using AWS VS Toolkit.
Describe the solution you'd like
Support for interpreting a profile's
credential_process
parameter in~/.aws/credentials
Please see:
Describe alternatives you've considered
Using a scheduled task to run external process for refreshing session token and injecting a static profile into
~/.aws/credentials
.I did a cursory glance but did not identify if this is built on top of aws-sdk-net. If so I'll submit the appropriate feature request there as well.
The text was updated successfully, but these errors were encountered: