configuring-connected-apps

What problem does it solve?

Configuring Salesforce OAuth correctly—especially across Connected Apps and External Client Apps (ECAs)—is error-prone and security-sensitive, and missteps can break authentication or expose credentials.

Core Features & Use Cases

• Connected Apps & ECAs Setup: Generate and configure OAuth app metadata for Salesforce integration use cases, including server-to-server and user-interactive flows.
• OAuth Flow Selection & Configuration: Guide the right flow choice (Authorization Code, PKCE, JWT Bearer, Device Flow, Client Credentials) and apply the correct metadata templates.
• Security Scoring & Guardrails: Provide a 120-point validation approach with best-practice defaults like least-privilege scopes, explicit callback URLs, PKCE for public clients, and rotation-ready strategies.
• Migration Support: Assist with Connected App → ECA migration planning and mapping, including retrieval-first requirements for certain ECA security settings.
• Deployment Readiness & Error Handling: Validate file naming/suffix conventions and surface common failure causes like duplicate apps, cross-reference mismatches, and insufficient permissions.

Quick Start

Use configuring-connected-apps to create an External Client App named "MobileApp" with PKCE enabled for a mobile client that needs Api and RefreshToken scopes.