Skip to main content

v0.6.1

nauth-toolkit team

Fixed​

  • MySQL returned numbers where the API promises booleans. If you run nauth on MySQL, responses could contain "isActive": 1 instead of true, and any code comparing such a field strictly — yours or the toolkit's — silently took the wrong branch. Postgres was never affected.

The stored schema is unchanged, so there is no migration to run. Upgrade and the values come back as booleans.

Three consequences you may have seen:

SymptomNow
An MFA device's isPreferred was false on every device, even right after setting a preferenceReflects the preference
A forced password change never challenged the user at sign-inChallenges as configured
Administrative MFA-exemption checks did not take effectApplied correctly

If you worked around the first one by reading preferredMethod from mfa/status instead of the device list, that workaround stays valid — the devices list is simply accurate now too.