SSO users get error when trying to register an MFA device "It's not you, it's us"
Hi All,
All of my users are getting an error when trying to set up an Authenticator app in their MFA settings via the user portal. The users are brought to the Register MFA device screen and can choose a type and hit next, but then are presented with an error stating "It's not you, it's us. We couldn't complete your request right now. Please try again later."
Current settings:
- Users should be prompted for MFA: always-on
- Users can authenticate with these MFA types: Authenticator apps
- If a user does not yet have a registered MFA device: Require them to register MFA device at sign in
- Who can manage MFA devices: Users can add and manage their own MFS devices
- Identity Source: AWS SSO
I have tried various other configurations with the same results. I can assign MFA devices to users from the SSO console as an administrator. Are there other settings I'm missing?
Thank you
What is your identity source in this configuration?
Sorry I should have included that, AWS SSO.
Please open a support case and we can get this resolved for you. https://docs.aws.amazon.com/awssupport/latest/user/case-management.html
Relevant questions
Unable to register a Grafana new Workspace. Network Failure trying to setup AWS SSO as authentication method.
asked 2 months agoCognito set user MFA required when using TOTP only
asked 3 months agoGetting Error Message after entering MFA code on GovCloud admin account
asked a year agoSSO users get error when trying to register an MFA device "It's not you, it's us"
asked 2 months agoAWS Service Catalog. Grant SSO Users to the Portfolio
asked 2 months agoError when trying to add db instance to VS server explorer
asked 3 years agoIs it possible to assign MFA for AWS IAM role?
asked 5 months agoPush a container to Lightsail with AssumeRole and MFA
Accepted Answerasked 4 months agoCan not add MFA or add users I see an error page flashing
asked 15 days agoCognito TOTP MFA issue
asked 2 years ago
I have the same issue, which also started three days ago. Did this get resolved?