Cache behaviour

[callmekatootie]

1. The token cached uses the client id. However, the client id and the audience combination is unique and not just the client id.
2. In tag 2.6.4, the cache exists outside the exported function for m2m. In 2.6, it exists within the function.

Thus, I can use 2.6 for my scenario where I have same client id but different audience but I cannot use 2.6.4, since it returns the token with the incorrect audience, even if we set it up with a new audience