-
Notifications
You must be signed in to change notification settings - Fork 357
Support entering otpauth://
URIs in details
#990
Comments
The easiest solution might be to just encode the |
Would this be necessary to achieve something like the Authy push messages (see also this issue) or should this already work out of the box since #393 was implemented? |
I see. So this would be another scheme then, right?
I'm aware of that. As far as I understood the architecture, Unified Push usually needs a backend that's compatible to it (i.e. ntfy, NextPush or Gotify). But I have no insights about Android development or its requirements for opening apps. That's why I asked. |
Is your feature request related to a problem? Please describe.
Currently, all my TOTP codes are in apps that save and display them in the edit screen as
otpauth://
URIs. That makes them easy to copy and paste. As of now, there is no option to enter the full URI via the "enter details" option.Describe the solution you'd like
It would be great, if there was an option next to TOTP, HOTP, MOTP & Steam to enter full
otpauth://
URIs.Describe alternatives you've considered
From the
otpauth://
URI, it is possible to extract all the parameters to enter them separately into the form fields. It just takes a lot more work and requires a certain degree of precision.Additional context
Apps and services using the
otpauth://
URIs are e.g. 1Password & Bitwarden.The text was updated successfully, but these errors were encountered: