[ 
https://issues.apache.org/jira/browse/CAMEL-13464?focusedWorklogId=235728&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-235728
 ]

ASF GitHub Bot logged work on CAMEL-13464:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 01/May/19 09:19
            Start Date: 01/May/19 09:19
    Worklog Time Spent: 10m 
      Work Description: Duvel commented on pull request #2897: [CAMEL-13464] 
Olingo4: use endpointHttpHeaders for EDM, solving authentication issue
URL: https://github.com/apache/camel/pull/2897
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 235728)
            Time Spent: 10m
    Remaining Estimate: 0h

> Problem with Olingo4 and authenticated metadata
> -----------------------------------------------
>
>                 Key: CAMEL-13464
>                 URL: https://issues.apache.org/jira/browse/CAMEL-13464
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-olingo4
>    Affects Versions: 2.23.2
>            Reporter: Remco Schoen
>            Priority: Minor
>         Attachments: headers_fix.diff
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> I'm currently working with the Olingo4 component for linking with Microsoft 
> Dynamics 365 CRM. This OData feed requires authentication to get the 
> metadata. As I have to refresh the Access Token for authenticating I can not 
> add it to the configuration, but I'm using the 
> CamelOlingo4.endpointHttpHeaders header for this. But when the component is 
> retrieving the metadata it is ignoring the header and it is not able to 
> authenticate.
> If I add the headers to the get metadata request it works.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to