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

Google Authenticator import error: "Label contains a colon" #103

Closed
richard-kramer opened this issue Jul 22, 2022 · 5 comments
Closed

Google Authenticator import error: "Label contains a colon" #103

richard-kramer opened this issue Jul 22, 2022 · 5 comments
Labels
bug Something isn't working fixed The issue is fixed (in a coming release)
Milestone

Comments

@richard-kramer
Copy link

Describe the bug

Import via the google authenticator (#74) is currently not possible. When scanning the export QR-code, the accounts seem to be imported with the naming scheme domain:username. 2FAuth marks these names as invalid, because they contain a colon and provides no method of changing them.

To Reproduce
Steps to reproduce the behavior:

  1. Open "Google Authenticator" on your smartphone
  2. Click on the context menu -> transfer accounts -> export accounts
  3. select accounts
  4. Login to 2FAuth
  5. Click on "New"
  6. scan export QR-code from the authenticator app

Expected behavior

My accounts from Google Authenticator get imported into 2FAuth and I can generate tokens for them.

Screenshots

Bildschirmfoto vom 2022-07-22 12-49-27

Desktop (please complete the following information):

  • OS: Ubuntu 20.04
  • Browser: Chrome
  • Version: 103.0.5060.114

Smartphone (please complete the following information):

  • Device: OnePlus 7T Pro
  • OS: Oxygen OS 11.0.8.1 (Android 11)
  • Browser: Chrome
  • Version: 103.0.5060.71
@Bubka
Copy link
Owner

Bubka commented Jul 22, 2022

Weird, It looks like the export format on Android might be different than the one on iOS, it's really unexpected.

Do you have the ability to export fake accounts and provide me the QR code? I don't have any Android device to test with.

@richard-kramer
Copy link
Author

Of course, there you go:

Screenshot 2022-07-22 155156

@Bubka
Copy link
Owner

Bubka commented Jul 22, 2022

Assumption confirmed thanks to your code. Not a big deal to fix but I need to understand why/when the formats differ. What version of G-Auth are you running?

@Bubka Bubka added the bug Something isn't working label Jul 22, 2022
@Bubka Bubka moved this to Todo in 2FAuth backlog Jul 22, 2022
@Bubka Bubka added this to the v3.3 milestone Jul 22, 2022
@Bubka Bubka moved this from Todo to In Progress in 2FAuth backlog Jul 22, 2022
@richard-kramer
Copy link
Author

Version 5.20R4

@Bubka Bubka moved this from In Progress to Done in 2FAuth backlog Jul 25, 2022
@Bubka Bubka added the fixed The issue is fixed (in a coming release) label Jul 25, 2022
@Bubka Bubka closed this as completed in 8e397fb Aug 1, 2022
@Bubka Bubka moved this from Done to Released in 2FAuth backlog Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working fixed The issue is fixed (in a coming release)
Projects
Status: Released
Development

No branches or pull requests

2 participants