title: Pass decoded JWT payload to micro services
body: <p>We are changing our application authentification architecture to switch to Json Web Token.</p>
  
  <p>Actually, incoming requests first pass through an API Gateway that dispatch requests to various micro services of our stack.</p>
  
  <p><strong>The authentification and verification of the JWT passed in each request is done in the Gateway.</strong></p>
  
  <p>After authentification what would you do with the JWT ?</p>
  
  <ol>
  <li>Pass it 'as it' to the subsequent micro services ?</li>
  <li>Decode it in the gateway and only pass the decoded payload to the services ?</li>
  </ol>
  
  <p>I see pro and cons in both solutions:</p>
  
  <ol>
  <li><p><strong>Pro:</strong> we keep a standard Authentification http header all the way. 
  <strong>Cons:</strong> We have to decode the token in each service. </p></li>
  <li><p><strong>Pro:</strong> Token is already decoded and directly usable in services. 
  <strong>Cons:</strong> We must use a non standard http header to pass the decoded payload. </p></li>
  </ol>
  
  <p>Is there any 'standard' way in that situation ?</p>
  
  <p>What's your opinion ?</p>
  
  <p>Thanks !</p>