BAD_FORMAT error when 'nbf' claim is set to 0 in the JWT token issued by RH-SSO
Issue
- The
nbf
claim found in a generated RH-SSOaccess_token
is always set with a value of0 (zero)
. This can cause aBAD_FORMAT
error when consuming such a token with the Google API endpoints - How can we set the
nbf
claim in theaccess_token
(JWT) with a dynamic value higher than 0 (for example with a value closer to theiat
claim value)?
Environment
- Red Hat Single Sign-On (RH-SSO)
- 7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.