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

Feature request: Add otpauth as a safelisted scheme for protocol registration handling #2204

JakeChampion opened this issue Dec 21, 2016 · 1 comment


Copy link

commented Dec 21, 2016

Section of the spec this relates to -->

Description of problem:
I have a web application which handles storing and generating time-based one-time-passwords (TOTP). Most services which implement multi-factor authentication (MFA/2FA) surface the otpauth link as a QR-code for the user to scan. I would like to register my web application to handle these links, much like native applications can such as Google Authenticator and Authy.

Add otpauth to the safelisted scheme list, this will mean user-agents will no longer throw a "SecurityError" DOMException.

This is the change I would like to make:

 - bitcoin
 - geo
 - im
 - irc
 - ircs
 - magnet
 - mailto
 - mms
 - news
 - nntp
 - openpgp4fpr
+- otpauth
 - sip
 - sms
 - smsto
 - ssh
 - tel
 - urn
 - webcal
 - wtai
 - xmpp

This comment has been minimized.

Copy link

commented Jun 12, 2017

Closing per #2205 (comment)

@domenic domenic closed this Jun 12, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.