Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Fri, 2 May 2014 05:18:15 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12710997.1398713430788.217892.1399007895634@arcas>
In-Reply-To: <JIRA.12710997.1398713430788@arcas>
References: <JIRA.12710997.1398713430788@arcas>
Subject: [jira] [Commented] (CAMEL-7398) Salesforce recently changed their
 login API to use new OAuth fields, which breaks the camel-salesforce
 component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CAMEL-7398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987344#comment-13987344 ] 

Claus Ibsen commented on CAMEL-7398:
------------------------------------

Yeah its resolved now, as the fix is on all needed branches.

> Salesforce recently changed their login API to use new OAuth fields, which breaks the camel-salesforce component
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-7398
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7398
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-salesforce
>    Affects Versions: 2.13.0
>            Reporter: Dhiraj Bokde
>            Assignee: Dhiraj Bokde
>            Priority: Critical
>             Fix For: 2.13.1, 2.14.0
>
>
> Salesforce added new fields to the login API response. These fields should be added to the LoginToken DTO. 


--
This message was sent by Atlassian JIRA
(v6.2#6252)