Closed ismail44 closed 8 months ago
How is the Settings check list set up? Uncheck them all and try it.
Does your username start with AWSReservedSSO_
after logging into AWS MC?
Thanks for the reply.
All boxes are unchecked... and the permission set I choose is:
AWSReservedSSO_(rolename)_ca8fexxxxxxxx/{my email}
@ismail44 Just to confirm, is the _
included in the ca8fexxxxxxxxxx
? If so, it may cause this problem.
If account alias is set as shown below, you must also define aws_account_alias.
[base-sso]
aws_account_id = 000011112222
aws_account_alias = company
role_name = some_permission_set
That worked like a charm!!! Thanks.
On Oct 24, 2023, at 8:02 AM, Toshimitsu Takahashi @.***> wrote:
If account alias is set as shown below, you must also define aws_account_alias.
https://user-images.githubusercontent.com/519017/277650102-4a6ca228-b477-4614-b05f-bb02dc21cec5.png [base-sso] aws_account_id = 000011112222 aws_account_alias = company role_name = some_permission_set — Reply to this email directly, view it on GitHub https://github.com/tilfinltd/aws-extend-switch-roles/issues/299#issuecomment-1777073070, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALKBT6ILQCTUWJAC4PMSYDYA6U5RAVCNFSM6AAAAAA3AHZ472VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZXGA3TGMBXGA. You are receiving this because you were mentioned.
Describe the bug Cannot see "target roles" when logged into "base role" using AWS SSO.
To Reproduce Steps to reproduce the behavior:
Expected behavior I would expect that by logging into the role identified by base2-sso, I would see base2-assumeable-role in my dropdown.
Environment