[
https://issues.apache.org/jira/browse/CAMEL-10779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15857661#comment-15857661
]
ASF GitHub Bot commented on CAMEL-10779:
----------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1448
> Authentication : provide a way to use refresh_token mode in addition to
> password method
> ---------------------------------------------------------------------------------------
>
> Key: CAMEL-10779
> URL: https://issues.apache.org/jira/browse/CAMEL-10779
> Project: Camel
> Issue Type: Improvement
> Components: camel-salesforce
> Reporter: Mabrouk Belhout
> Assignee: Zoran Regvart
> Priority: Minor
> Labels: authentication, oauth2
> Fix For: 2.19.0
>
>
> We had to connect to a Salesforce partner instance. Our partner did not
> provide login/password but instead a clientid clientsecret and refreshtoken.
> Today in camel-salesforce component, authentication is forced to be
> login/password based.
> This improvement should provide an alternative using refresh_token method of
> oauth.
> Objective is to enrich the
> _SalesforceSession.getLoginRequest(HttpConversation)_ method and add
> {{fields.put("grant_type", "refresh_token");}}
> as an alternative to
> {{fields.put("grant_type", "password");}}
> this has impacts on _SalesforceLoginConfig_ class and other authentication
> involved classes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
