-
Notifications
You must be signed in to change notification settings - Fork 101
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
sso client should not check for creds #207
Comments
We're looking into this. We have a few possible ways to handle this case, and need to figure out which solves the problem in the most general way without breaking things or introducing new dependencies. Please stand by. |
@benjamin-asdf when I run your example with a dummy profile configured, I get this:
Is that the validation err you get? |
(aws/invoke
(aws/client {:api :sso})
{:op :GetRoleCredentials
:request {:accessToken "fo"
:roleName "role"
:accountId "id"}}) ;; without dummy #:cognitect.anomalies{:category :cognitect.anomalies/fault, :message "Unable to fetch credentials. See log for more details."} ;; with dummy ~/.aws/credentials
yea seems to be the same |
Dependencies
e.g.
Repro
It fails too early in this case.
Sso should be a specail case where it doesn't look for creds because the use
case is that you fetch exactly those creds.
workaround:
configure a default profile (with keys)
set system props to some dummy values etc.
The text was updated successfully, but these errors were encountered: