talk
talk copied to clipboard
INTERNAL_ERROR: TOKEN_INVALID: jwt not active
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.

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