Closed cedieio closed 6 months ago
The recent feature for assume --export-sso-token is causing panic when being run.
--export-sso-token
This is due to cred-exporter.go not having the correct key when finding the cached token below. It should have the correct key for finding the token.
cred-exporter.go
-cachedToken := secureSSOTokenStorage.GetValidSSOToken(profile.AWSConfig.SSOStartURL) +tokenKey := profile.AWSConfig.SSOStartURL + profile.AWSConfig.SSOSessionName +cachedToken := secureSSOTokenStorage.GetValidSSOToken(tokenKey)
Another is when finding the plain text sso token is using the tokenKey := profile.AWSConfig.SSOStartURL + profile.AWSConfig.SSOSessionName which should not be the case as the token is being queried using the profile.AWSConfig.SSOStartURL
tokenKey := profile.AWSConfig.SSOStartURL + profile.AWSConfig.SSOSessionName
profile.AWSConfig.SSOStartURL
it should be
-plainTextToken := GetValidSSOTokenFromPlaintextCache(ssoTokenKey) +plainTextToken := GetValidSSOTokenFromPlaintextCache(profile.AWSConfig.SSOStartURL)
The recent feature for assume
--export-sso-token
is causing panic when being run.This is due to
cred-exporter.go
not having the correct key when finding the cached token below. It should have the correct key for finding the token.Another is when finding the plain text sso token is using the
tokenKey := profile.AWSConfig.SSOStartURL + profile.AWSConfig.SSOSessionName
which should not be the case as the token is being queried using theprofile.AWSConfig.SSOStartURL
it should be