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
After testing support for AzureAD AWS Federation (#165) and logging into our environment I found that the AWS role name does not appear correctly when the AWS Role is in a path.
Leapp Version
Fork of 0.6.2 with Pull Request #165
To Reproduce
Steps to reproduce the behavior:
Create a new Session
Click on 'AWS'
Click on 'IAM Role Federated'
Fill out the details and use a Role ARN that is in a path such as arn:aws:iam::123456789123:role/CAVM/AVM_app_dev
See error
Expected behavior
I would expect to see the role name "AVM_app_dev" or the entire role path "CAVM/AVM_App_dev"
Screenshots
The text was updated successfully, but these errors were encountered:
Thanks for reporting; we need to fix the method that extracts the last part from the ARN.
We'll try to fix this for the next release, I think it should be easy.
Describe the bug
After testing support for AzureAD AWS Federation (#165) and logging into our environment I found that the AWS role name does not appear correctly when the AWS Role is in a path.
Leapp Version
Fork of 0.6.2 with Pull Request #165
To Reproduce
Steps to reproduce the behavior:
arn:aws:iam::123456789123:role/CAVM/AVM_app_dev
Expected behavior
I would expect to see the role name "AVM_app_dev" or the entire role path "CAVM/AVM_App_dev"
Screenshots
The text was updated successfully, but these errors were encountered: