Validating parser saml
The same security principles apply when storing or caching bearer tokens for later use.
Always ensure that your app transmits and stores bearer tokens in a secure manner.
When your app receives an id_token, it must validate the signature to prove the token's authenticity and validate a few claims in the token to prove its validity.
The claims validated by an app vary depending on scenario requirements, but there are some common claim validations that your app must perform in every scenario.
Id_tokens are a form of sign-in security token that your app receives when performing authentication using Open ID Connect.
Note that the claims in id_tokens are not returned in any particular order.
You can use the claims in an id_token as you see fit - commonly they are used for displaying account information or making access control decisions in an app.
Id_tokens are signed, but not encrypted at this time.
In addition, new claims can be introduced into id_tokens at any point in time - your app should not break as new claims are introduced.
The following list includes the claims that your app can reliably interpret at the time of this writing.