camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhiraj Bokde (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-8519) Salesforce component security listener does not replace old auth header
Date Fri, 20 Mar 2015 03:14:38 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dhiraj Bokde updated CAMEL-8519:
--------------------------------
    Summary: Salesforce component security listener does not replace old auth header  (was:
Salesforce component session listener does not replace old auth header)

> Salesforce component security listener does not replace old auth header
> -----------------------------------------------------------------------
>
>                 Key: CAMEL-8519
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8519
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-salesforce
>    Affects Versions: 2.13.4, 2.14.2, 2.15.0
>            Reporter: Dhiraj Bokde
>            Assignee: Dhiraj Bokde
>             Fix For: 2.14.3, 2.15.1
>
>
> The security listener incorrectly adds a copy of the auth header for streaming api client.
Although this causes the exchange to ultimately fail, the BayeuxClient reconnects and proceeds
without raising errors in Camel route. However, this ends up logging multiple warnings from
the security listener and the BayeuxClient. 
> Fixing the security listener to reset the auth header will optimize this process and
let the BayeuxClient continue with the existing exchange. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message