-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Failed to add Microsoft 365 QR Code because colon character in account field #134
Comments
Regarding the validation step failure, please set the Secret field as |
Another point: unless specified (like in the given Microsoft example), algorithm is SHA1. You screen shows a SHA256 config. |
Thanks! the print is with sha256, but I tested all the algorithms, including sha1, removing the organization and colon from account and validation fail. the secret is a smaller string, like this generated now: "7yfnlbbyt2ldtsnw" |
You can, this has no impact on generated password.
Simply uppercase the string, it should works. |
That's it!!!!! its working now! For future searches
|
Describe the bug
The Test feature returns an error in the advanced form when the account field contains a colon.
The qrcode generated by Microsoft also is not accepted by upload feature.
Removing the colon, the generated otp is not accpeted by Microsoft validation.
Related to issue #45
To Reproduce
Steps to reproduce the behavior:
Go to /account/create
Field the form with Account or Service with a colon
Click on Test
See error
Removing the colon, the validation step with the generated otp with Microsoft fail.
Example QR Code text generated by Microsoft
otpauth://totp/ORGANIZATION:account@domain.com?secret=xxxxxxFAKExxxxx&issuer=Microsoft
Expected behavior
An OTP password should be displayed and validation success
Additional context
Version 3.4.0 using docker hub image 2fauth/2fauth:3.4.0
Same error on version 3.3.3
Screenshots
The text was updated successfully, but these errors were encountered: