This is an issue related to OTPs scanned with URI. If the QR-encoded URI lacks the issuer string in the label, a pop-up message appears, suggesting that you add the issuer. It also gives you the option to proceed with adding the OTP without the issuer. However, this results in duplicate tokens.
Technically, OTP URI contains an important parameter which is the label. Labels usually contain issuer and account strings e.g. google:user@gmail.com where google is the issuer and after delimiter : comes the account. Some systems don't provide issuer string in label parameter. Also, the optional parameter &issuer=foo could be missing too resulting into this issue .
Hello everyone,
This is an issue related to OTPs scanned with URI. If the QR-encoded URI lacks the issuer string in the label, a pop-up message appears, suggesting that you add the issuer. It also gives you the option to proceed with adding the OTP without the issuer. However, this results in duplicate tokens.
Technically, OTP URI contains an important parameter which is the label. Labels usually contain issuer and account strings e.g.
google:user@gmail.com
wheregoogle
is the issuer and after delimiter:
comes the account. Some systems don't provide issuer string in label parameter. Also, the optional parameter&issuer=foo
could be missing too resulting into this issue .Example strings from such systems:
The above URI as QR code:
Steps to reproduce
next
.Use empty issuer
.Enviroment:
Best