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
Valid SSO credentials aren't accepted by client #2934
Comments
Hi @micah-press sorry for the delay in response. Are the SSO credentials set in the default profile? If it is, it's indeed weird that V2ProfileCredentialsProvider is not picking them up. Can you show the format of your sso credentials in your profile file? Please redact the real values, I'm only interested in the attribute names to see if I can recreate them for my local tests. |
Yep, I've been running
Do you mean my config file or my SSO credentials cache file? |
The config file. |
All our profiles look like this:
|
Any other information I can provide? |
Please keep us posted if anyone found a workaround or solution to this. |
Is there anything else I can help with? |
Describe the bug
I'm attempting to use the v1 and v2 Java AWS SDKs side by side. I'd like to support loading SSO credentials and use them to initialize v1 client objects. When I try to do this with a client (S3 in this case), I get an exception:
However, if I set up a profile using the Access Key, Secret Key, and Session Token generated from the SSO credentials, I'm able to authenticate successfully through the AWS CLI.
Expected Behavior
If I can generate a valid Access Key and Secret Key from a set of credentials, I should be able to initialize a client and make calls with it.
Current Behavior
The client rejects the Access Key ID, saying it doesn't exist on the backend.
Reproduction Steps
I've got an SSCCE at https://github.com/micah-press/aws-sdk-sscce.
Possible Solution
No response
Additional Information/Context
I wrote some shims/wrappers to implement the v1 credentials and providers interfaces using v2 objects. They're contained in the repo linked above.
AWS Java SDK version used
1.12.332 and 2.20.12
JDK version used
openjdk version "11.0.18" 2023-01-17
Operating System and version
Ubuntu 20.04.5 LTS
The text was updated successfully, but these errors were encountered: