v1.16.1Web App
•1 min read

Authenticator secrets are now encrypted at rest

The secret seed behind your authenticator app codes is now encrypted with AES-256-GCM before it is saved. Until now it was stored unencrypted, so anyone able to read the database could have generated valid 2-Step Verification codes.

You don't need to do anything. Your authenticator app keeps working with the same seed, and you won't need to enroll again. Setting up or replacing an authenticator also works as before.

Seeds are encrypted with a key managed by the server, not with a project's custom vault key, because they are needed during sign-in before any vault is unlocked.

For more on sign-in security, see the authentication documentation.