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
When using SSO and the new AWS multi-session sign-in, the account name is no longer recognized and displayed. It seems to default to the account id. This should be corrected to recognize the account name when multi-session sign-in is enabled.
Reproduction Steps
Enable multi-session sign-in on an AWS account. Login using SSO. The account name is not displayed in the console (just account id).
Sign in Method
Direct login to target account via AWS SSO
Direct login to target account via IAM user
Login to a jump account via AWS SSO, then switch role to target account
Login to a jump account via IAM user, then switch role to target account
Sign in as the root user
Browser Name
Chrome
Browser Version
131.0.6778.265
Other information
Muli-session sign-in was just released. No rush.
The text was updated successfully, but these errors were encountered:
Thanks for the report, @casumner45 san!
Your Issue made me aware of the need for Multi Session support. Appreciate it.
I have looked into the Multi Session specs in detail and it seems that the display has changed significantly and also supports the display of account aliases. Therefore, we are currently working on a policy to support this as Peacock.
(See more at #95)
It may take 1~2 weeks to resolve this issue, but we hope you can wait. Your comments are welcome!
What is the problem?
When using SSO and the new AWS multi-session sign-in, the account name is no longer recognized and displayed. It seems to default to the account id. This should be corrected to recognize the account name when multi-session sign-in is enabled.
Reproduction Steps
Enable multi-session sign-in on an AWS account. Login using SSO. The account name is not displayed in the console (just account id).
Sign in Method
Browser Name
Chrome
Browser Version
131.0.6778.265
Other information
Muli-session sign-in was just released. No rush.
The text was updated successfully, but these errors were encountered: