title: Vault reports missing client token when using postgres storage backend
body: <p>I am using Vault with postgres storage backend along with kv secret engine. I am uisng kubernetes auth method to get the vault token. I followed the below documentation to setup the vault with kubernetes</p>
  <pre><code>https://learn.hashicorp.com/tutorials/vault/kubernetes-minikube?in=vault/kubernetes
  </code></pre>
  <p>When I start the webapplication for the first time and try to retrieve the tokens it is working but when I delete the webapp deployment and try to deploy webapp again and try to retrieve the vault token again with the api</p>
  <pre><code>v1/auth/kubernetes/login
  </code></pre>
  <p>I get the following error</p>
  <pre><code>error: 400 Bad Request: [{&quot;errors&quot;:[&quot;missing client token&quot;]}
  </code></pre>
  <p>But the request has the jwt token of service account. Please see the below image
  <a href="https://i.stack.imgur.com/HXSnE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/HXSnE.png" alt="Wireshark capture of the request" /></a></p>
  <p>Due to this error Pod keeps restarting and all of a sudden after some time vault honours the request and returns the vault token.</p>
  <p>This looks strange any reason for such behavior?</p>
  <p><strong>UPDATE:</strong></p>
  <p>This issue does not happen for consul backend</p>