You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When you have a role that requires MFA, that is assumed from another account, when the MFA session expires Leapp can no longer connect and gives the following error:
User: <PARENT ACCOUNT USER> is not authorized to perform sts:AssumeRole on resource <ASSUME ROLE>
Leapp Version
0.18.1
To Reproduce
Steps to reproduce the behavior:
Create two AWS accounts - I'll call them parent and child
Add MFA to your root account
Create a role in your child account with the following policy (below)
Expected behavior
I should be allowed to reconnect to the assume role as I have permission.
I believe this is an issue with the session not being correctly cleared or reprompting for MFA.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS] MacOS Ventura
OS Version [e.g. 22] 13.6
Leapp Version [e.g. 0.2.5] 0.18.1
Additional context
Thanks for the great software! I recommend it all the time :) ✌️
The text was updated successfully, but these errors were encountered:
Describe the bug
When you have a role that requires MFA, that is assumed from another account, when the MFA session expires Leapp can no longer connect and gives the following error:
User: <PARENT ACCOUNT USER> is not authorized to perform sts:AssumeRole on resource <ASSUME ROLE>
Leapp Version
0.18.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I should be allowed to reconnect to the assume role as I have permission.
I believe this is an issue with the session not being correctly cleared or reprompting for MFA.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Thanks for the great software! I recommend it all the time :) ✌️
The text was updated successfully, but these errors were encountered: