1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
Hi there,
Sorry to hear about any trouble this might've caused. Our teams value your perspective, which is why I've flagged your thoughts on this experience to our internal team for further review. For secure guidance on any account concerns, please open a case in the Support Center here: https://go.aws/support-center.
Thank you,
- John M.
関連するコンテンツ
AWS公式更新しました 2年前- AWS公式更新しました 3年前
Hello again Alon,
Our re:Post team heard you feedback on this experience and wanted to share an update with you. They've announced two new methods for authenticating to re:Post. You can now link multiple logins or sign in without using your AWS account. If you haven't had the chance, please check out the details here: https://aws.amazon.com/about-aws/whats-new/2022/12/aws-repost-customers-community-engagement-builder-id-repost-linked-logins.
If this solution isn't what you're looking for or you spot opportunities for improvement, we'd love to hear from you. To get the details reviewed for further consideration, please select the feedback button on the right side of the screen.
Thanks again for raising your perspective on this!
- John M.
Hello John,
I am glad that aws introduced the builder id, however, it does not respect SSO setting of organization and require different credentials management.
Linking accounts to the repost is infinite task as every new account in organization requires manual activity. One of many simple approach would be to prompt for email and then login using the specific account that is linked to the email address, so that email x@x.com will prompt account 1232145 login which will trigger the SSO as applied for the organization.
I also could not find a way to merge the existing profile into a single profile, when I select "link account" it complains that the source account already has a profile so it refuses to link/merge it.
Regards,