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

We have a service configured as follows:

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

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

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

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