title: Authorization header not passed by ZuulProxy starting with Brixton.RC1
body: <p>In switching from Spring Cloud <code>Brixton.M5</code> to <code>Brixton.RC1</code> my ZuulProxy no longer passes <code>Authorization</code> headers downstream to my proxied services. </p>
  
  <p>There's various actors in play in my setup, but most all of them are fairly simple:
  - AuthorizationServer: runs separately; hands out JWTs to clients
  - Clients: get JWTs from OAuth server; each with access to a subset of resources.
  - ResourceServers: consume JWTs for access decisions
  - MyZuulProxy: proxies various resource servers; should relay JWTs.</p>
  
  <p>It should be noted that MyZuulProxy has no security dependencies whatsoever; It passed the <code>Authorization: Bearer {JWT}</code> header it receives to the ResourceServers, pre-RC1. MyZuulProxy is explicitly not a Client itself, and does not use <code>@EnableOAuth2SSO</code> or similar at the moment.</p>
  
  <p>What could I do to get MyZuulProxy to relay the JWTs to the ResourceServers again when using Spring Cloud Brixton.RC1?</p>
  
  <p>There's very little code to post: It's just <code>@EnableZuulProxy</code>, <code>@EnableAuthorizationServer</code> and <code>@EnableResourceServer</code> in three different jars. My Clients are not Spring applications.</p>