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

v0.24.5 unable to extract token from client #359

Closed
abatilo opened this issue Aug 9, 2022 · 0 comments · Fixed by #362
Closed

v0.24.5 unable to extract token from client #359

abatilo opened this issue Aug 9, 2022 · 0 comments · Fixed by #362

Comments

@abatilo
Copy link
Contributor

abatilo commented Aug 9, 2022

⇒  aws-oidc configure --issuer-url=https://example.com/ --client-id=aws-config --config-url=https://example.com --default-region us-east-1 --default-role-name readonly
Error: Unable to extract token from client: could not read from keyring: encoding/hex: odd length hex string
FATA[0000] Unable to extract token from client: could not read from keyring: encoding/hex: odd length hex string

Hi all. Just wanted to give a heads up that it appears that maybe a dependency update that was released with v0.24.5 is causing an invalid state or assertion of some kind.

I downgraded to v0.24.4 and didn't have any problems with the exact same command.

pull bot pushed a commit to tangerinehuge/aws-oidc that referenced this issue Nov 18, 2023
It appears that the [following
change](zalando/go-keyring@v0.1.1...v0.2.0#diff-14c4aa5420de20b1ef5b174be7c1d389e4bdbbf71719ca66bf308caf38c60d1dR66-R93) in `zalando/go-keyring` is causing the problem described in chanzuckerberg#359. While we figure out how to fix this upstream, downgrade the version used in `aws-oidc` to stop breakages of new uses of `aws-oidc`.

Closes chanzuckerberg#359
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 a pull request may close this issue.

1 participant