Closed mitchellrj closed 2 years ago
i think this is more an issue than an enhancement :). Thanks Richard for reporting this.
PowerShell (PromptForChoice)[https://docs.microsoft.com/en-us/dotnet/api/system.management.automation.host.pshostuserinterface.promptforchoice] capability is limited to shortcuts being a single character and case insensitive.
In order to address this we would need to reimplement PromptForChoice. I will investigate this further.
hello, any update on this issue? I have got the same problem, I am using AWS tools for PowerShell and have more than 26 roles to assume. The alphabets run out after [Z] and the remaining roles show up without any character.
We have noticed this issue has not recieved attention in 1 year. We will close this issue for now. If you think this is in error, please feel free to comment and reopen the issue.
Expected Behavior Assuming a role via SAML should allow the user to use any role in the returned claim.
Current Behavior
Set-AWSSamlRoleProfile
to authenticate and get a list of roles that may be assumedZ
, the options are displayed, but there is no means of selecting them.Possible Solution
Steps to Reproduce (for bugs)
Set-AWSSamlRoleProfile
Context Workaround is to specify the role on the command line using the
-PrincipleArn
and-RoleArn
options, but this is not very user friendly.Your Environment Include as many relevant details about the environment where the bug was discovered.
Get-AWSPowerShellVersion
: 3.3.542.0$PSVersionTable.OS
: Windows 10 (1809) (suggested command returns no value)$PSVersionTable.PSEdition
: 5.1.17763.1 (Desktop)