|
|
This is not yet actionable since there is no spec documented. I found this example in the Taler POS " taler-pos://backend.demo.taler.net/#/username=<username>&password=<password> " which uses an unusual fragment to separate the params from url and access token is not supported. |
|
|
I have created this draft implementation to check how PoS creates the config but no look with the POS app image.png (90,320 bytes) image-2.png (29,091 bytes) image-3.png (61,311 bytes) |
|
|
5949a356a..a2fe54a89 only visible on expert mode |
|
|
Firstly, about the #, yes, a bit not standard, but I guess this was a move to make sure that backend logs do not contain usernames and passwords. From what I see, the QR code you have sent is recognized by pos, the only problem in my case was the fact that the merchant.taler is not found :(((( Otherwise, absolutely valid point about access tokens, I will try to make a DD for this in the next couple of days, just for the matter of structure, quite sure it will be "taler-pos://backend.demo.taler.net/#/username=<username>&access_token=<token>" |
- Anonymous
