Join our Newsletter — 33% off our NHI Course
Home› FAQ› Governance, Ownership & Risk› What breaks when direct login is still enabled…
Governance, Ownership & Risk

What breaks when direct login is still enabled in Salesforce after SSO is deployed?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 31, 2026 Domain: Governance, Ownership & Risk

When direct login remains enabled, the application keeps a second authentication path that can bypass the identity provider. That breaks the central enforcement model for access policy and creates a gap between intended governance and actual behavior. It also increases the chance that password resets, weaker credential policies, or brute force attempts can succeed.

Why a second login path breaks Salesforce SSO governance

Direct login is not just an extra convenience path. If users can still authenticate with Salesforce credentials after SSO is deployed, the org now has two different trust decisions for the same account. That weakens policy consistency, complicates enforcement, and makes it harder to prove that the identity provider is the true control point for access.

When you enable SSO, the goal is usually to centralise authentication, MFA, conditional access, and recovery controls at the identity provider. If direct login remains live, those controls may be bypassed for some sign-in attempts, so the org’s actual authentication behavior no longer matches the intended architecture.

That is why SSO rollouts should be treated as control migrations, not just UI changes. The important question is whether every path into the application is governed by the same policy and audit model, including help-desk recovery, break-glass access, and any legacy credentials that still exist in the background.

What operational control gaps appear when both paths stay open?

The main gap is inconsistent enforcement. One path may require phishing-resistant MFA, device or location checks, and federation logging, while the fallback local login path may permit weaker password-based access. That creates an uneven control surface that attackers can target and defenders may not notice until an account is used through the weaker route.

It also creates ambiguity for account ownership and troubleshooting. If a user is locked out of SSO but direct login still works, support teams may re-enable or preserve the weaker route to keep the business moving. Over time, that exception can become the normal operating state unless it is actively removed.

Direct login can also distort monitoring. Authentication events, reset events, and anomaly signals are harder to interpret when some logins flow through the identity provider and others do not. A clean deployment should make the login path visible enough that you can tell which control actually authenticated the session.

Why attackers prefer the leftover direct-login path

A remaining password path gives attackers a simpler target than federated access. They can try password spraying, credential stuffing, or reuse of older credentials without having to defeat the identity provider’s stronger policy stack first. If the org assumes SSO is the only path, that weaker route becomes an easy gap in the defense model.

This is especially risky when password resets or account recovery still allow a local credential to be re-established. In that case, the attacker does not need to break federation. They only need enough access to trigger the weaker path, then use it before the issue is detected.

Legacy login paths also make session and recovery abuse more likely. If a user can regain access outside the central SSO process, the org may lose visibility into whether the recovery action was legitimate, socially engineered, or part of an account takeover chain.

Risk and Threat Considerations

Leaving direct login enabled after SSO deployment creates a parallel authentication channel that can be abused as an alternate entry point. The risk is not theoretical, because the weaker path often preserves older credential habits, fallback recovery logic, and less consistent policy enforcement.

Failure mechanism: Users, support staff, or attackers can still reach the application without passing through the identity provider’s full access policy, which means the central control plane no longer fully governs sign-in.

Impact: This can lead to policy bypass, weaker authentication outcomes, harder incident investigation, and a larger account-takeover surface if old passwords or recovery paths remain usable.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5, NIST CSF 2.0 and OWASP ASVS set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Direct login after SSO changes user authentication enforcement.
IA-5 — Authenticator ManagementResidual passwords and reset paths sustain the bypass risk.
Recommendation — Require all user sign-ins to flow through the controlled authentication path. Disable or tightly govern leftover credentials and recovery pathways.
NIST CSF 2.0PR.AA-05 — Identity Management, Authentication and Access ControlSSO migration is about enforcing one access policy across login paths.
Recommendation — Centralise authentication policy and eliminate alternate access paths.
OWASP ASVSV10 — OAuth and OIDCFederated SSO depends on correct identity-provider-driven authentication flows.
Recommendation — Validate that federation is the only intended authentication route.
ISO/IEC 27001:2022A.5.15 — Access controlDual login paths undermine consistent access enforcement and governance.
Recommendation — Document and enforce one approved access path for the application.

Practitioner Guidance

What to verify: Confirm that direct authentication is disabled for all standard users, not just hidden from the UI. Test both normal login and recovery flows, because a clean SSO rollout can still fail if password reset, emergency access, or delegated administration reopens the local path.

Decision rule: If any account can still authenticate outside the identity provider, treat that as an incomplete migration and close the gap before declaring the SSO rollout finished. If business-critical exceptions are unavoidable, scope them tightly, time-bound them, and review them as privileged access exceptions.

What good looks like: Every routine sign-in follows the same federation path, the fallback path is disabled or tightly controlled, and sign-in telemetry clearly shows when an exception is used. For a practical hardening baseline, see the Salesforce Security Guide and the Identity Provider and SSO Security Guide.

Practitioner takeaway: SSO only centralises access if every normal login path is actually forced through it, so the real control objective is to remove the fallback, not merely add federation.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org