What problem does it solve? Setting up OAuth-enabled Salesforce Connected Apps or External Client Apps involves choosing the right app model, OAuth flow, scopes, and security policies, and small metadata mistakes (wrong file suffixes, missing fields, wildcard callbacks) cause deployment failures or security gaps. This Skill guides the full configuration workflow and validates the result against a 120-point security checklist. ## Core Features & Use Cases - App Generation from Templates: Create Connected Apps or External Client Apps from pre-built XML templates covering basic API, full OAuth, JWT bearer, Canvas, and ECA companion metadata files. - OAuth Flow Selection: Decision guidance for Authorization Code, PKCE, JWT Bearer, Device, and Client Credentials flows based on client type and use case. - 120-Point Security Scoring: Validate existing or new apps across six categories including PKCE, scope least-privilege, callback URLs, and token rotation. - Migration Support: Step-by-step guidance for migrating Connected Apps to External Client Apps, including credential rollover and cutover planning. - Use Case: A DevOps engineer needs a CI/CD integration and asks for a JWT bearer Connected App with a certificate; the Skill generates the correct .connectedApp-meta.xml, applies hardening rules, and reports a security score. ## Quick Start Use the integration-connectivity-connected-app-configure skill to create an External Client App named FieldServiceMobile with PKCE enabled and Api, RefreshToken, and OpenID scopes.
