talk icon indicating copy to clipboard operation
talk copied to clipboard

INTERNAL_ERROR: TOKEN_INVALID: jwt not active

Open yogeshbeniwal opened this issue 3 years ago • 0 comments
trafficstars

Expected behavior: Login with OpenID Connect should work with Azure AD B2C

Actual behavior: Login with OpenID Connect is throwing INTERNAL_ERROR: TOKEN_INVALID: jwt not active error. However testing with https://jwt.ms/ shows jwt is returned in response by Azure AD B2C and same configuration is working for other OpenID client applications.

Screen Shot

This may be because of time clock difference, hence related to #4040

yogeshbeniwal avatar Aug 30 '22 17:08 yogeshbeniwal