TLDR: Where in the

SuperTokensConfig

would we intercept this error and revoke the existing token so the user is asked to login again? After someone has logged in, when switching the front end to different Supertokens instances we get the following error:

Bearer scope="" error="invalid_token" error_description="unable to find an appropriate key in the JWKS. Ensure a "kid" is provided in the JWT, and that your JWKS has a supported cert available for this ID"

Which makes total sense. When this error happens on the backend, we would like to revoke the token so the user can login again. Is this possible, and if so, where in the

SuperTokensConfig

would we do this?