-
Notifications
You must be signed in to change notification settings - Fork 19.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(Salesforce Node): Add support for PKCE #14082
feat(Salesforce Node): Add support for PKCE #14082
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅ 📢 Thoughts on this report? Let us know! |
displayName: 'Grant Type', | ||
name: 'grantType', | ||
type: 'hidden', | ||
default: 'pkce', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Joffcom wouldn't changing default break existing credentials? they had to be reconnected, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michael-radency I didn't have to reconnect my existing credential but you are right, it is possible that on refresh it errors out though. Let me see if I can think of a way to test that. Originally I was thinking about using a toggle option for PKCE but for some reason the grant type didn't like working with an expression.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@michael-radency I connected my local env using non PKCE then used this branch and it has been running all weekend with no issues so I don't think this will break anything.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
n8n
|
Project |
n8n
|
Branch Review |
node-873-salesforce-add-pkce-support-to-the-credential
|
Run status |
|
Run duration | 04m 53s |
Commit |
|
Committer | Jonathan Bennetts |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
1
|
|
5
|
|
0
|
|
472
|
View all changes introduced in this branch ↗︎ |
Can you merge latest master and rerun e2e? Curious if that fixes the 49-folders issue Edit: It probably won't! Feel free to ignore the failed tests in 49-folders |
…ce-add-pkce-support-to-the-credential
✅ All Cypress E2E specs passed |
Got released with |
Summary
Enables PKCE support for Salesforce, Turns out if you don't have PKCE enabled in Salesforce it will still allow it to be used so the option they have is to enforce it.
Related Linear tickets, Github issues, and Community forum posts
https://linear.app/n8n/issue/NODE-873/salesforce-add-pkce-support-to-the-credential
https://community.n8n.io/t/salesforce-credentials-bug-with-code-challenge/31845
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)