We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As a user connecting to Salesforce, I'd like to be able to use an Oauth2 connection rather than my username/password/securityToken.
We will probably need to create a Salesforce connected app for the global OpenFn instance (app.openfn.org) and another for testing locally (localhost:4000) - https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htm
app.openfn.org
localhost:4000
From @aleksa-krolls : Customers will need different scopes depending on their requirements and there could be use cases for using all sorts of combos of these. I think usually we’d need refresh_token, id, api… and maybe full or lightning (not our lighting) but we should build the adaptor in a way we can change these. See this docs article for more on scopes: https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_tokens_scopes.htm&language=en_US&type=5
refresh_token
id
api
full
lightning
The text was updated successfully, but these errors were encountered:
Hey team! Please add your planning poker estimate with Zenhub @midigofrank @stuartc @elias-ba @jyeshe
Sorry, something went wrong.
expires_at
elias-ba
Successfully merging a pull request may close this issue.
User story
As a user connecting to Salesforce, I'd like to be able to use an Oauth2 connection rather than my username/password/securityToken.
Details
Implementation notes
We will probably need to create a Salesforce connected app for the global OpenFn instance (
app.openfn.org
) and another for testing locally (localhost:4000
) - https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/intro_oauth_and_connected_apps.htmFrom @aleksa-krolls : Customers will need different scopes depending on their requirements and there could be use cases for using all sorts of combos of these. I think usually we’d need
refresh_token
,id
,api
… and maybefull
orlightning
(not our lighting) but we should build the adaptor in a way we can change these. See this docs article for more on scopes: https://help.salesforce.com/s/articleView?id=sf.remoteaccess_oauth_tokens_scopes.htm&language=en_US&type=5Release notes
User acceptance criteria
The text was updated successfully, but these errors were encountered: