3 Replies Latest reply on Jun 12, 2014 1:42 PM by bas.kuis

    Authorization header not included when jive routes requests to add-on service


      We have a service configured as follows:

      Screen Shot 2014-06-11 at 7.50.43 PM.png


      And when sending a POST to the endpoint using Jive connects:


      Screen Shot 2014-06-11 at 7.54.15 PM.png


      We see that the headers do not include the Authorization header like we would expect:


      Screen Shot 2014-06-11 at 7.55.22 PM.png


      This is resulting in a unauthorized response. Please note the 'test':'yo' header that was added to the service configuration:


      Screen Shot 2014-06-11 at 7.56.52 PM.png


      This seems to indicate that the expected service (and configuration) routes the request correctly to the expected add-on service definition.


      Ryan Rutan - Mark Weitzel - is this due to a misunderstanding on my part on how this is supposed to function or are we missing something? For instance - does the authorization header only get sent over https? Why could it be that the Authorization header isn't passed along to the middle-ware?


      cc: John Larson, Ben Liesch