sf-connected-apps

Configure Salesforce Connected Apps and External Client Apps with OAuth security policies.

423|97|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/Jaganpro/sf-skills --skill sf-connected-apps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sf-connected-apps
Source: https://github.com/Jaganpro/sf-skills/tree/main/sf-connected-apps/skills/sf-connected-apps
Command: npx skills add https://github.com/Jaganpro/sf-skills --skill sf-connected-apps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) components.

What problem does it solve?

Configuring Salesforce Connected Apps and External Client Apps (ECAs) with correct OAuth settings and security best practices is complex and critical for secure integrations. This Skill automates their creation and validation, reducing security risks and configuration errors.

Core Features & Use Cases

  • App Generation: Create Connected Apps and ECAs with OAuth 2.0 configuration, scopes, and callbacks, tailored to your specific use case (e.g., API integration, SSO, mobile apps).
  • Security Review: Analyzes OAuth configurations for critical security best practices like PKCE, refresh token rotation, IP restrictions, and appropriate scope usage.
  • Migration Guidance: Provides assistance and recommendations for migrating from older Connected Apps to the more secure and modern External Client Apps.
  • Use Case: Generate an External Client App for your new mobile application, ensuring PKCE is enabled, minimal OAuth scopes are granted, and all security best practices are followed for a robust and secure integration.

Quick Start

Use the sf-connected-apps skill to create an External Client App for a mobile application with PKCE enabled.

Frequently Asked Questions about sf-connected-apps

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Salesforce Connected Apps with OAuth 2.0 security best practices?

Configure Salesforce Connected Apps by enabling PKCE, setting minimal OAuth scopes, enforcing refresh token rotation, and applying IP restrictions. This Skill automates app creation with built-in security validation across JWT Bearer, PKCE, and standard OAuth flows to reduce misconfiguration risks.

What's the difference between Salesforce Connected Apps and External Client Apps, and when should I migrate?

External Client Apps are the modern, more secure alternative to Connected Apps with enhanced OAuth 2.0 capabilities and stronger policy compliance. Migrate when you need improved security controls, better token management, and compliance with current Salesforce best practices for integrations.

How do I ensure my Salesforce OAuth integration meets security compliance requirements?

This Skill validates OAuth configurations against 120-point security scoring across six categories, checking PKCE enforcement, token rotation policies, certificate management, and scope appropriateness. It flags compliance gaps and provides remediation guidance for single-org and multi-org deployments.

Can I use this Skill to secure existing Salesforce integrations without rebuilding them?

Yes. The Skill provides migration guidance and templates to upgrade existing Connected Apps to External Client Apps while maintaining current integrations. It assesses your configuration, identifies security gaps, and recommends deployment pathways for zero-downtime transitions.

What OAuth flows does this Skill support for different Salesforce integration scenarios?

This Skill supports JWT Bearer, PKCE, and standard OAuth flows tailored to your use case—API integrations, SSO, and mobile apps. Each flow includes app generation templates, pre-configured scopes, and security enforcement specific to your deployment context.

How does PKCE improve security for my Salesforce mobile app integrations?

PKCE adds a dynamic cryptographic layer to OAuth that prevents authorization code interception attacks, critical for mobile apps where code can be exposed. This Skill enforces PKCE by default and validates its implementation across your OAuth configuration.