Like most things, it depends. If you control the authorization server (i.e. your API that you are calling), I really do not see any problems reading the contents of the token on the client side.
If you call a third-party API and authenticate on a server that you do not control, I would not depend on the contents of the JWT token. A third party may decide to change the requirements in the token or even start encrypting the token.
source
share