Why is step-up authentication forced and buggy?
Step-up authentication is currently enforced without an option to turn it off, leaving administrators stuck with inconsistent browser behavior that support writes off as known issues. These unpredictable prompts prevent users from completing basic workflows, such as returning to their original report tab after verification.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
Found another way around this?
Share your steps and trade-offs so fellow engineers don't have to reinvent the wheel. No account required.
- 1Using different browsers like Edge or Chrome to see varying resultsDid this help you?
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
“I know there are still some outstanding known issues with step up authentication but we are getting different results in almost every environment haha.”source ↗
“In chrome, it doesn’t go to classic and it downloads after passkey id but opens on a different tab & stays on the id verification screen and doesn’t go back to the report tab.”source ↗
“Salesforce just keeps telling me to follow the known issues but besides the classic thing, our issues seem different.”source ↗
“All i know is every one of our users wants it disabled. This should not be forced on us if we are fine with our own security of our company.”source ↗
Where this came up
People with this problem also raised
- 9Why am I getting DMARC and SPF errors when emails deliver fine?
- 5Fixing security token enrollment errors for non-technical users
- 10Account deactivated for security reasons and stuck in ID verification loop
- 2Why does accounting software force logins for every company file?
- 7How to set up MFA backup methods so you don't get locked out
- 14Why am I getting locked out of my account when using the correct password?