Said It Here

Why do privileged Salesforce users have to create separate passkeys?

Salesforce forces administrators and privileged users to set up platform-specific passkeys instead of letting them use their existing enterprise SSO and MFA providers like Microsoft Authenticator. This requirement prevents teams from maintaining a unified authentication workflow across all users.

OverviewLatest thread: Sep 2026
People affected2 accounts (1 forum)
Workarounds found2 items recorded
Discussion timelineSep 2026
Freshness statusActive Consensus
Editorial ConsensusSynthesized across r/salesforce · Sep 2026
Verification standards →

Core Friction Pattern

Analysis of 2 peer accounts across online developer and community forums reveals that “Why do privileged Salesforce users have to create separate passkeys?” 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.

Top Peer-Reported Fix
Using the SOAP API instead of OAuth

+1 alternative community-tested workaround cataloged below.

Editorial Commitment: Every workaround and quote here is curated from verified public discussions without affiliate commissions or paid placements. Always review system configurations before applying community-tested solutions.

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.

Active Consensus (Latest: Sep 2026)Indexed across peer discussions from Sep 2026 to Sep 2026
Evaluated against breaking changes & deprecations
  1. 1
    Using the SOAP API instead of OAuth
    Did this help you?
  2. 2
    Setting up a Flow to set the ProfileId before a new user gets created
    Did 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.

r/salesforce2 people · September 2026

“Normal users can authenticate using Microsoft Authenticator, but privileged users are being forced to create a separate Salesforce passkey.”source ↗

“Is a passkey or phishing-resistant MFA now mandatory for all privileged Salesforce users? Is there any supported way for privileged users to continue using Microsoft Authenticator push through Entra SSO without creating a Salesforce passkey?”source ↗

Parking_Management_1 · r/salesforceSep 2026· 4 upvotes

“We have this all working just fine using the SOAP API, but since Salesforce is deprecating it, we need to switch to OAuth with an external client app... so we're doing that, but we get this error: "REQUIRED_FIELD_MISSING:user_must_have_one_entitlement_which_must_be_a_profileid"”source ↗

“The thing is, we ARE applying the "profileId" attribute and the correct ID is being used. Looks like other people have had this problem recently as well, but we don't know how to fix it”source ↗

MowAlon · r/salesforceSep 2026· 4 upvotes

Where this came up

People with this problem also raised

Related community dilemmas clustered by discussion consensus

6 related topics

How do you manage accounts and passwords that don't use SSO?

Break-glass accounts, contractor logins, and apps without SAML or OIDC often end up scattered in shared vaults, duplicated across teams, or owned by someone who leaves the company. Without a way to rotate, audit, or assign clear ownership, these credentials become a compliance risk and a single point of failure during critical deadlines.

4 workarounds3 accounts · 2 forums

Can multiple Windows users open a KeePass database?

KeePass does not natively support setting up multiple Windows user logins or Active Directory domain accounts as valid authentication for a single database. This prevents shared systems from allowing different users to open the file using their individual credentials.

2 workarounds2 accounts · 1 forum

How to handle SSO and device management for local AD and M365?

Hybrid environments combining local Active Directory, Microsoft 365, and remote VPNs lack a unified way to handle credentials across separate domains. This disconnect prevents cloud-identity users from signing in to local machines and breaks centralized device management.

3 workarounds2 accounts · 1 forum

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.

8 workarounds5 accounts · 1 forum

Staying logged into apps when your identity provider goes down

Centralizing login through a single identity provider leaves you vulnerable when it fails, and authenticator apps can stop working during an outage. Long token lifetimes and offline access policies only buy a few hours of breathing room before access drops, and many SaaS apps do not support break-glass accounts or alternate login methods. Past 12 hours of downtime, businesses that rely on that provider can be brought to a standstill.

7 workarounds6 accounts · 1 forum

How to share MFA for a shared admin account

SaaS platforms increasingly require multi-factor authentication for shared integration accounts, but standard methods like push notifications tie access to a single engineer's phone. This creates a single point of failure that prevents other administrators from logging in to fix broken integrations. Teams are forced to either risk using a single device or put the second factor in a password vault, which locks them out of everything if the vault goes down.

9 workarounds6 accounts · 2 forums