docs: Update Salesforce auth docs for Salesforce Spring '26 (External Client Apps)#920
Conversation
…Client App Salesforce Spring '26 removed the "New Connected App" button from App Manager. New apps must be created as External Client Apps. Existing Connected Apps continue to work. Updated both Connected App auth sections to reflect the new UI flow. Related: SUPPORT-16320 Co-Authored-By: tereza.skalova <tereza.skalova@keboola.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
@ZdenekSrotyr — requesting your review since you merged the previous Salesforce auth docs update in PR #858. |
|
@keboola-pr-reviewer review |
![keboola-pr-reviewer[bot]](https://avatars.githubusercontent.com/u/1424387?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
There was a problem hiding this comment.
🚩 Incomplete terminology rename: "Connected App" reference remains in Additional Settings
Line 80 still reads (available for Security Token and Connected App methods) while all the section headers and descriptions in this PR were renamed from "Connected App" to "External Client App". This creates an inconsistency — a user reading the updated section headers won't find a method called "Connected App" anymore. This line wasn't touched by the diff, but it should be updated to match the new terminology (e.g., "External Client App methods").
(Refers to line 80)
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Good catch — fixed in cf10a30. Updated "Connected App methods" → "External Client App methods" on line 80.
There was a problem hiding this comment.
Verdict: needs_human (risk 3/5) · profile docs
This PR introduces substantive product-behaviour claims about Salesforce External Client App setup steps that require human verification.
Concerns:
components/extractors/marketing-sales/salesforce/index.md: PR body admits ECAs may not support password grant type, making the Username+Password section potentially incorrect guidance.components/extractors/marketing-sales/salesforce/index.md: Heading renames break old anchor slugs; inbound links to #connected-app-with-username-and-password are now silently broken.components/extractors/marketing-sales/salesforce/index.md: Step 4 ('Distribution State → Local') is flagged by the author as unverified — based on a customer report only.
Suggested reviewers: keboola/docs
…enamed sections Co-Authored-By: tereza.skalova <tereza.skalova@keboola.com>
matyas-jirat-keboola
deleted the
docs/salesforce-external-client-app-spring-26
branch
Brings in everything merged on main since 2026-03-20 (PRs #888 through #920), including: - Telemetry: dashboards rewrite (#900-class), connector docs migrated to YAML+include (#896-class), new kbc_mcp_event table, alphabetical ordering, ER diagram viewer - Data Apps: storage-access docs (#914, #910), backend-versions index rename, streamlit config.toml docs (#917), nav restructure - Custom Python component docs (#888), Salesforce External Client App Spring '26 updates (#920), Governed Change Management (#918) - Public-beta-warning refactor (now 2 instances total) Sidebar regenerated with new entries. Telemetry-data Liquid loops are now expanded via the new transform (50 tables rendered, 0 Liquid tags left in the page).
2 participants
Jira issue(s): SUPPORT-16320
Changes:
Context: Salesforce Spring '26 (Jan/Feb 2026) removed the "New Connected App" button from App Manager. New integrations must use "New External Client App." The Keboola connector config fields (
consumer_key,consumer_secret,domain) remain identical — no connector code changes needed.Steps verified against: Salesforce blog post on ECAs, AuditForce step-by-step guide, Salesforce Trailhead ECA project, and Salesforce developer docs on Client Credentials + Run As user.
Items for reviewer to verify:
grant_type=passwordflow per Salesforce docs, but the connector may use a different grant type (e.g., device flow or auth code) under the hood#external-client-app-with-username-and-passwordin the CC section cross-reference resolves correctly in Jekyll — verified via local testingFollow-up needed (not in this PR):
keboola/component-salesforce-v2/README.mdhas the same outdated Connected App setup steps and needs a separate PR (kds-team-owned).Previously updated in PR #858 (Dec 2025, pre-Spring '26).
Link to Devin session: https://app.devin.ai/sessions/05b283f4bb2c47889bee0ad70042d8bd
Requested by: @terezaskalova