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
{{ message }}
This repository has been archived by the owner on Oct 24, 2024. It is now read-only.
Many 2FA-enabled websites do not allow the private token to be displayed or redisplayed, such as when authenticating Pebble after authenticating another device. However, the QR codes are generally allowed to be displayed and redisplayed for authenticating multiple devices.
So it would be helpful if QuickAuth supported tokens added via QR code images, using the phone's camera to capture them.
I'm currently mitigating this by deleting my old tokens/QR codes, and setting up 2FA from scratch on each account, making sure to copy the manual token into QuickAuth before it is made unavailable as part of the 2FA setup process on different websites.
The text was updated successfully, but these errors were encountered:
I completely agree and have even made a version of the html configuration page that does exactly that. I unfortunately the Pebble app does not have camera permissions and they have ignored my requests to add it. Secondly Safari for ios doesn't support access to the camera. IE does but not Safari.
Please email Pebble asking for camera support within the configuration paves. If more people ask they might listen.
Many 2FA-enabled websites do not allow the private token to be displayed or redisplayed, such as when authenticating Pebble after authenticating another device. However, the QR codes are generally allowed to be displayed and redisplayed for authenticating multiple devices.
So it would be helpful if QuickAuth supported tokens added via QR code images, using the phone's camera to capture them.
I'm currently mitigating this by deleting my old tokens/QR codes, and setting up 2FA from scratch on each account, making sure to copy the manual token into QuickAuth before it is made unavailable as part of the 2FA setup process on different websites.
The text was updated successfully, but these errors were encountered: