Explore technology. Understand yourself.

💬 In plain words: A Connected App is the security contract between your Salesforce org and an external application. It defines which OAuth 2.0 flows the integration may use, which scopes (token permissions) it can request, which users are allowed to authenticate, and what session or IP policies apply. As Salesforce transitions toward External Client Apps (ECAs) —which separate developer configuration from administrator policies and are closed by default—understanding how both models govern API access is essential for every architect and developer. 📌 Illustrative Integration Scenario: Imagine a partner integration request lands on your desk in 2026. Instead of creating a classic Connected App (where creation may be restricted by default in newer org configurations to encourage modern standards), you provision an External Client App , configure it for the OAuth 2.0 JWT Bearer or Client Credentials flow, and grant access strictly through an assigned Permission S...

💬 In plain words: Single Sign-On (SSO) lets users log in once with a trusted provider and enter connected applications without re-entering credentials. Security Assertion Markup Language (SAML 2.0) is an established XML-based standard commonly used for corporate workforce directories like Microsoft Entra ID or Okta. OpenID Connect (OIDC) is a modern JSON-based identity layer built on OAuth 2.0, suited for mobile apps and consumer portals such as "Login with Google." Both protocols verify identity and establish a valid Salesforce session. 📌 Illustrative Dual-SSO Architecture: Picture a company running a single Salesforce org for both staff and customers. Internal employees authenticate through corporate Microsoft Entra ID using SAML 2.0 SSO on the org's My Domain login page—one employee credential covers their daily tools. Meanwhile, external users on the Experience Cloud customer portal sign in via "Login with Google," powered by an Op...