title: Is it okay to Cache verified JWT token to prevent repeated verification process in spring-boot application
body: <p>We have a spring-boot appplication with microservice architecture.
  <br> We have a separate service for Authentication which provides a JWT token signed with RS256 algorithm.<br>This token is sent in every request from client to our main application server.
  I have the public key for verifying the signature.
  <br>Now this JWT token is being sent in every API request from client side as most of our URLs are protected.
  <br><br>Is it a good idea to cache the already verified JWT token to prevent repeated verification process of same token on every API call from same user? </p>