Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

otpauth URIs with padding in the secret are not accepted #1759

Open
jonasbb opened this issue Jan 11, 2025 · 0 comments
Open

otpauth URIs with padding in the secret are not accepted #1759

jonasbb opened this issue Jan 11, 2025 · 0 comments

Comments

@jonasbb
Copy link

jonasbb commented Jan 11, 2025

When adding a new account via the QR code, I get an input validation error on the secret key field. The message states, "Invalid format, allowed characters: a-z2-7". This happens because the secret value contains some padding at the end. Padding seems to be allowed, just discouraged: https://docs.yubico.com/yesdk/users-manual/application-oath/uri-string-format.html#secret

otpauth://totp/Example:[email protected]?secret=AA======&issuer=Example

image

This is a problem, because when adding an account via QR code I cannot edit the secret key to remove the trailing padding. So this forces me to add the account fully manually.

Please consider either allowing padding for the secret key, i.e., expanding the allowed characters to include =, or to strip them before filling the UI elements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant