title: Spring Cloud Config with Git/Vault backend - token passthrough
body: <p>Instead of giving an AppRole or Static Token for Spring Cloud Config Server to access <strong>ALL</strong> secrets across <strong>ALL</strong> applications, is it possible to configure Spring Cloud Vault Config to utilize a given token on the request for the configuration?</p>
  
  <p>This communication would be over 2-way SSL with the token in the headers. Not ideal to send such a token outward but seems the proper solution in this scenario.</p>
  
  <p>Keep in mind this is a Spring Cloud Config Server using Git + Vault as backends in order to resolve secrets, variables, etc, into the desired configurations. This would not only be used for Spring Configurations but other files delivered to an ephemeral environment, such as an httpd.conf for Apache (bad example to shove secrets into)</p>
  
  <p>Goal here is to limit access where possible and keeping it limited to the end-application requesting the configuration. Also nice to not duplicate RBAC efforts with AuthZ on Spring Config <strong>AND</strong> Vault policies.</p>