-
Notifications
You must be signed in to change notification settings - Fork 168
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
Chamber is not working with recommended AWS SSO config that uses sso-session #396
Comments
@jim-barber-he can you confirm what your current
We recently released an updated version that brought us up to latest for |
Ah sorry, the version information is pretty important...
Okay, that was purely speculation on my part with nothing to back it up. I was hoping the fix would be as easy as that. :) |
@jim-barber-he got it, thanks! On a whim, do you mind checking out latest All that should be necessary is |
I get the same result.
|
Thanks for checking! Looking into it a little, we may need to bump to |
It looks like a pull request to add support to it was raised 3 hours ago: So with any luck, once this is merged and a release of |
The support for |
Updated Will resolve this with a release |
v2.13.2 is now release which should resolve this problem for you @jim-barber-he Let me know if all is good (and feel free to close out the issue if so) |
With the old AWS config the new version works as did the old one.
With the new
|
Hmm, alright. It looks like that might be coming from internals of the We unfortunately don't have the configuration to test this out currently and it might take some time to get running. If you want to continue digging and end up finding a fix, we'd be happy to accept a contribution. |
Hey @jim-barber-he, I just merged in #411 which included the following bug fix from the
(Related Issue: aws/aws-sdk-go#4912) Do you mind trying a local build off of latest |
Yep it looks good:
vs the other one I have that is broken (not using
|
@jim-barber-he Great! I'll trigger a release then |
Closing this as done thanks to https://github.com/segmentio/chamber/releases/tag/v2.13.3 |
AWS IAM Identity Center (formerly known as AWS SSO) has two ways of being configured.
There's the recommended way that uses sessions with automatic token refresh: https://docs.aws.amazon.com/cli/latest/userguide/sso-configure-profile-token.html
And the old legacy way: https://docs.aws.amazon.com/cli/latest/userguide/sso-configure-profile-legacy.html
Chamber works fine with the legacy method, however it does not work with the recommended method.
Legacy:
Recommended:
Redacted legacy config in
~/.aws/config
:Redacted recommended config in
~/.aws/confg
:I suspect the fix will be to update the aws-sdk-go dependency
The text was updated successfully, but these errors were encountered: