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.
Core Friction Pattern
Analysis of 2 peer accounts across online developer and community forums reveals that “Why is step-up authentication forced and buggy?” repeatedly surfaces due to edge-case mismatches between standard defaults and real-world environments. Standard troubleshooting frequently falls short, compelling practitioners to develop custom workarounds.
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.
Why is step-up authentication forced and buggy?
- 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
Related community dilemmas clustered by discussion consensus
Why does Salesforce require another login after Okta 2FA?
Salesforce does not recognize Okta's 2FA as sufficient, forcing users to jump through multiple verification processes just to gain access. This creates an awful "MFA all the time" workflow that puts up a barrier to actually accessing the system. Ultimately, these extra security hoops make it even harder to get sales teams to use the tool.
Why does Outlook keep asking me to sign in after an outage?
Stale cached tokens and shorter sign-in sessions after an outage can trigger repeated authentication prompts in Outlook and M365. These pop-ups can keep appearing for hours even when mailflow still works, while others run into periods where work Outlook goes down completely.
Why am I getting DMARC and SPF errors when emails deliver fine?
Third-party email marketing services often fail basic SPF checks within DMARC reports because their sending IPs are not included in your domain's DNS records, even though inbox providers still manage to deliver the messages. This discrepancy leaves administrators guessing about real deliverability health and creates confusing tool warnings that hinder proper configuration.
Fixing security token enrollment errors for non-technical users
Asking standard employees to manually navigate certificate tools, templates, and provisioning slots turns simple token setups into 30-minute helpdesk calls. Additionally, strict configurations cause sign-ins to fail with error messages stating that the passkey does not meet the criteria set by the admin.
Why are phishing emails bypassing Exchange Online Protection?
Clean phishing emails are being delivered straight to the inbox with no warning from Exchange Online Protection. These spoofs sail through primarily because of per-user whitelists. When a client allowlisted a sender years ago, it causes these malicious emails to bypass current filtering entirely.
Account deactivated for security reasons and stuck in ID verification loop
Routine profile updates or edits frequently trigger sudden account deactivations without clear explanations or human support to resolve the issue. Submitting a government ID through third-party services like Persona or CLEAR often results in endless processing loops with no way to log in or contact customer service.