A successful setup-token login now also returns when that token expires.
What's wrong with this entry?
The success result of the setup-token login now includes the token's expiry time from the exchange, or nothing when the server did not supply one. Previously it carried only the token.
expiresAt: se.expiresAt ?? void 0
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Login refresh tells "account on hold" apart from an expired token
Both mention auth
-
v2.1.235
Full "account on hold" sign-in path built but switched off
Both mention auth
-
v2.1.235
On-hold accounts get their own auth failure kind, behind the same gate
Both mention auth