You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
When executing a KeePass export using the --mfaModenoninteractive-totp, specifying the --mfaTotpToken as is (with possible '===' padding thrown in at the end), throws the error:
Hi @Stenstromen, so the reason for the failure is because your mfaTotpToken is not a valid base32 string and only valid base32 can be used to generate totps. Can you try converting it from base64 to base32 and see if it works?
The string I use in my example is intentionally not valid, because it didn't feel right to use my actual live one.
My main point with this issue is that while the Passbolt WebUI TOTP Generator accepts a base32 string with padding added to the end as a valid one. Say 52F10769M85H704GWXJIVY39FPK8S3EZ02ZX5KVC598S91149WM2A==== (again, not an actual valid TOTP secret).
But the exact same string, with the padding added, is not considered valid by go-passbolt-cli. But when the padding at the end is removed, 52F10769M85H704GWXJIVY39FPK8S3EZ02ZX5KVC598S91149WM2A, it is considered valid by go-passbolt-cli --mfaTotpToken. (???)
Describe the bug:
When executing a KeePass export using the
--mfaMode
noninteractive-totp
, specifying the--mfaTotpToken
as is (with possible '===' padding thrown in at the end), throws the error:To Reproduce:
Run a export with mfaMode noninteractive-totp and specify the mfaTotpToken, like the following example:
Output when using --debug:
Passbolt Server Version:
go-passbolt-cli Version:
The text was updated successfully, but these errors were encountered: