options to store otpauth with the bare minimum form about keepassotp HOT 5 CLOSED

If you refer to the colon in {REF:U:I...} this will be fixed soon (today / tomorrow)
Placement of issuer and label fields is described and after #37 is fixed, there should be no malformed string anymore.
They canot occur all over the place.

Except the reference issue which results in a malformed otpauth string, it's up to each app to parse the otpauth string in a proper way.
I favour the idea of raising tickets for the respective app after I fixed the reference issue.

from keepassotp.

Issuer and label are not mandatory but every client should be able to either process them or - at least - to ignore them.

Which clients do have issues with a valid otpauth string containing isser and label?
best solution would be to have these clients corrected and enable them to properly use a valid otpauth string.

from keepassotp.

You are right. But it needs precise implementation to ignore label and issuer since these strings can be all over the place (nonascii, strange symbols, missed scenarios, etc). Add an option to just not include them will increase the tolerance of other clients (mostly mobile platform clients …).

One example is that KeePassDX (an android client) will be confused by the colon in the reference string 😂

from keepassotp.

If the handling of arbitrary string to url is not gonna be a problem (I mean in general, not the reference bug), then I have no other practical reason to back this feature.

from keepassotp.

The reference bug is fixed in the new release, in case you face additional issues I'll reopen this issue

from keepassotp.