End-user's device clock out of sync causes token expired error

[Blackbaud-PeteLukich]

Description

When an end-user signs in and their device's clock is not sync'd with an accurate time server, they can experience an issue such as "credentials_expired". This occurs because a token is created using the time of their device as specified in this community post:
https://community.auth0.com/t/the-credentials-has-expired-error-on-mfa-page/89005

Is there a way that we can create the token using a "current time" value that is sent down from the server, rather than obtained from the end-user's device? This would eliminate these errors that users experience and remove the reliance on their device's clock to be accurately sync'd with a server.

Reproduction

Sign in as a user who is flagged to be enrolled in MFA. After successfully authenticating, they will receive the "credentials_expired" error, where they were expected to be taken to MFA enrollment.

Environment

Please provide the following:

• Version of this library used:
• Version of the platform or framework used, if applicable:
• Other relevant versions (language, server software, OS, browser):
• any browser
• Other modules/plugins/libraries that might be involved: