Repository navigation
Client-side licence gate on integrated TOTP generation diverges from server behaviour #7950
Closed
gamersalpha
started this conversation in
General
Replies: 2 comments 1 reply
|
Not sure why you think this, but those codes just show and work fine when using Vaultwarden. |
0 replies
|
Fair — and that confirms the server side is doing its job. To be precise, I'm not What I'm seeing is version-specific on the client:
If the Web Vault shows the code and the mobile app doesn't, it's a client-side |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Context
Bitwarden's official documentation now states explicitly that the generation
of TOTP codes from the integrated authenticator is a Premium / paid-org feature,
while merely storing the seed is available to all accounts:
https://bitwarden.com/help/integrated-authenticator/
Vaultwarden, by design, has no concept of a licence and serves the TOTP seed
through the ciphers API regardless. This creates a predictable divergence for
self-hosters: the server returns the data, but the official client refuses to
render/generate the code.
What I observe
Server-side config was verified:
TOTP_ENABLEDis not set tofalse, sogeneration is enabled at the server level.
Why I'm raising this here
Not asking for a fix in Vaultwarden's Rust code — the gate is in the client.
Two things would genuinely help the self-hosting community:
Wiki / FAQ entry documenting that integrated TOTP generation depends on
the client build, and which client versions still generate codes against a
Vaultwarden backend. Right now users hit this and conclude their server is
misconfigured, when
TOTP_ENABLEDis fine.Confirmation of the intended behaviour — does Vaultwarden consider the
client-side premium gate a compatibility break it wants to track (like the
v2026.4.0
/prelogin/password/endpoint change), or explicitly out of scope?If out of scope, a one-line statement in the wiki is enough and I'll close this
myself.
Environment
/admin/diagnostics)All reactions