Bug with creating aws_session_token for IAM User credentials without MFA

Describe the bug Sessions created AWS IAM User Provider and without MFA have trouble accessing IAM resources. One obvious difference to other sessions is that the aws_session_token has quotes around it.

Leapp Version 0.9.0

To Reproduce Steps to reproduce the behavior:

1. Add a new Session in Leapp (AWS, IAM User)
2. Fill in credentials for user with full access to all AWS resources, but no MFA enabled.
3. Start the newly created session
4. Inside .aws/credentials there should be an entry with aws_session_token="..."
5. Try to access your own user aws iam get-user --user-name XXX --profile YYY
6. Receive error: An error occurred (InvalidClientTokenId) when calling the GetUser operation: The security token included in the request is invalid

Expected behavior The user information is fetched and shown in the console

Desktop (please complete the following information):

• OS: macOS
• OS Version 12.2.1
• Leapp Version 0.9.0

Additional context I tried the same AWS command with the same base credentials, but without temporary credentials and that works.

[deiga]

@ericvilla That is a very good point! But I still consider it a bug in Leapp, since I don’t have any way not to use temporary credentials

[rudeluv]

I just ran into the exact same issue, so I added my MFA device to the AWS IAM User configuration. However, I’m not prompted for an MFA code for some reason.

@jalaziz I realize this is old but I was running into the same problem. I had to delete the session and re-create it with the MFA device and after that it prompted me for a code.