salesforce-security-basics

Featured

Apply Salesforce security best practices for Connected Apps, OAuth, and field-level security. Use when securing API credentials, implementing least privilege access, or auditing Salesforce security configuration. Trigger with phrases like "salesforce security", "salesforce secrets", "secure salesforce", "salesforce connected app security", "salesforce FLS".

AI & Automation 2,926 stars 433 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 99/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Salesforce Security Basics ## Overview Security best practices for Salesforce integrations: Connected App configuration, OAuth scope management, field-level security, and credential rotation. ## Prerequisites - Salesforce org with System Administrator access - Connected App created in Setup > App Manager - Understanding of Salesforce security model (Profile, Permission Set, OWD) ## Instructions ### Step 1: Secure Connected App Configuration ``` Setup > App Manager > New Connected App: 1. Enable OAuth Settings 2. Callback URL: https://yourapp.com/oauth/callback (NOT localhost in prod) 3. Selected OAuth Scopes — USE MINIMUM REQUIRED: - "Manage user data via APIs (api)" — for REST/SOQL access - "Perform requests at any time (refresh_token, offline_access)" — for refresh tokens - DO NOT add "Full access (full)" unless absolutely necessary 4. Require Proof Key for Code Exchange (PKCE): Enable for public clients 5. Require Secret for Web Server Flow: Enable 6. IP Relaxation: "Enforce IP restrictions" (not "Relax IP restrictions") ``` ### Step 2: Credential Storage ```bash # .env (NEVER commit to git) SF_LOGIN_URL=https://login.salesforce.com SF_USERNAME=integration-user@yourcompany.com SF_PASSWORD=<from-vault> SF_SECURITY_TOKEN=<from-vault> SF_CLIENT_ID=<connected-app-consumer-key> SF_CLIENT_SECRET=<connected-app-consumer-secret> # .gitignore — ALWAYS include .env .env.local .env.*.local server.key # JWT private key *.pem *.key ``` ### Step 3: Use a Dedicate...

Details

Author
jeremylongshore
Repository
jeremylongshore/claude-code-plugins-plus-skills
Created
1 years ago
Last Updated
yesterday
Language
Python
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

salesforce-install-auth

Install and configure Salesforce SDK/CLI authentication with jsforce or Salesforce CLI. Use when setting up a new Salesforce integration, configuring OAuth flows, or initializing Salesforce connectivity in your project. Trigger with phrases like "install salesforce", "setup salesforce", "salesforce auth", "configure salesforce", "jsforce setup", "sf cli login".

2,926 Updated yesterday
jeremylongshore
AI & Automation Featured

salesforce-enterprise-rbac

Configure Salesforce Profiles, Permission Sets, and Sharing Rules for enterprise access control. Use when implementing role-based access, configuring SSO with Salesforce, or setting up organization-wide sharing defaults. Trigger with phrases like "salesforce permissions", "salesforce RBAC", "salesforce profiles", "salesforce SSO", "salesforce sharing rules", "salesforce OWD".

2,926 Updated yesterday
jeremylongshore
API & Backend Listed

sf-integration

Sets up and reviews Salesforce integrations — Named Credentials and External Credentials (creation, principal design, migration from legacy credentials and Remote Site Settings), OAuth flow selection, Platform Events (define/publish/subscribe/monitor/replay), Change Data Capture, and org-wide integration audits — MCP-first against the live org. Use when the user mentions a named credential, external credential, wants to connect to an external API, asks which OAuth flow to use, mentions platform events, CDC, change data capture, an integration audit, or callout setup. Do NOT use for creating custom objects and fields (use sf-metadata), scanning code for hardcoded secrets and vulnerabilities (use sf-security), or tracing callout failures and stalled subscribers in debug logs (use sf-debug). Usage: /sf-integration [credentials|events|cdc|review] {name} ...

5 Updated 2 months ago
kugamon