BAD_FORMAT error when 'nbf' claim is set to 0 in the JWT token issued by RH-SSO

Solution Verified - Updated -

Issue

  • The nbf claim found in a generated RH-SSO access_token is always set with a value of 0 (zero). This can cause a BAD_FORMAT error when consuming such a token with the Google API endpoints
  • How can we set the nbf claim in the access_token (JWT) with a dynamic value higher than 0 (for example with a value closer to the iat 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.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content