7.7 beta-2 - problems with QNAP login

PLMan

Since some 1Password upgrades it stopped to fill in user name when logging in to QNAP NAS devices. Creating new entry doesn't help. What is funny, build in iCloud password filling works…

---

1Password Version: 7.7 beta-2
Extension Version: 7.7 beta-2
OS Version: OS X 10.15.6
Sync Type: iCloud

rudy

@PLMan,

If possible, it would be helpful if you could:

Invoke 1Password mini
click on the gear menu
choose "request page json"
copy the text in the resulting safari tab and paste it here

PLMan

I have "request page json" item greyed out. How to enable it?

rudy

@PLMan,

it should automatically enable when you're looking at the page in safari when you click the gear, is that not happening?

PLMan

Nope, it is inactive on any page I'm visiting.

Gilles9

greyed out here too

rudy

@PLMan,

do you have Preferences -> Advanced -> Copy JSON turned off?

if you turn that on it should work.

Gilles9

@rudy
That was it, thanks

rudy

@PLMan,

:+1:

PLMan

Now it works. Here you have JSON:

{
"frames": [
{
"fields": [
{
"autocompleteType": "off",
"formOpid": 0,
"htmlClass": "qStr",
"htmlId": "pwd",
"opid": 0,
"placeholder": "Password",
"type": "password"
},
{
"autocompleteType": "off",
"formOpid": 0,
"htmlId": "rememStatus",
"isHidden": true,
"label": "Remember me",
"opid": 1,
"type": "checkbox",
"value": "on"
},
{
"autocompleteType": "off",
"formOpid": 0,
"htmlId": "secureStatus",
"isHidden": true,
"label": "Secure login",
"opid": 2,
"type": "checkbox",
"value": "on"
},
{
"formOpid": 0,
"htmlClass": "login-btn qStr submit",
"htmlId": "submit",
"labelBefore": "Secure login",
"opid": 3,
"type": "submit",
"value": "Login"
},
{
"autocompleteType": "off",
"formOpid": 0,
"htmlClass": "login_input",
"htmlId": "scyCode",
"isHidden": true,
"opid": 4,
"tabIndex": 1,
"type": "text"
},
{
"formOpid": 0,
"htmlClass": "login-btn qStr submit",
"htmlId": "scySubmit",
"isHidden": true,
"opid": 5,
"type": "submit",
"value": "Login"
},
{
"autocompleteType": "off",
"formOpid": 0,
"htmlClass": "login_input",
"htmlId": "scyAns",
"isHidden": true,
"opid": 6,
"tabIndex": 1,
"type": "text"
},
{
"formOpid": 0,
"htmlClass": "login-btn qStr submit",
"htmlId": "scyAnsSubmit",
"isHidden": true,
"opid": 7,
"type": "submit",
"value": "Login"
}
],
"forms": [
{
"htmlAction": "http://192.168.105.165:8080/cgi-bin/",
"opid": 0,
"textContent": "JTK-BIGNAS Remember me Secure login Login"
}
],
"origin": "http://192.168.105.165:8080",
"pathName": "/cgi-bin/",
"title": "JTK-BIGNAS",
"uuid": "tixdm3"
}
],
"title": "JTK-BIGNAS",
"unparsedUrl": "http://192.168.105.165:8080/cgi-bin/"
}

rudy

@PLMan,

Thanks, i've passed this along to the filling team to see if they can see where the filling solution generator is missing this particular form's fields.

PLMan

Great! I'm waiting for solution

rudy

@PLMan,

:+1:

mikeormerod

I have the same issue

ag_ana

Thank you for letting us know @mikeormerod! I have added your post to the issue tracker :+1:

ref: dev/core/core#2400

PLMan

We are almost one month later and what is going on with QNAP login problem?

rudy

@PLMan,

It looks like qnap may have goofed on their latest update? some have found a way to fix the goof: https://discussions.agilebits.com/discussion/112744/autofill-has-ceased-working-on-qnap-qts-4-4-2-1270-login-page/p1

PLMan

Do you really think, that users should modify their devices' config to make them working with 1Password? I think that 1P business is to fill logins and make it good. Competition has no problems with QNAP. So sorry, but password manager which is not filling passwords is just not useful. For years I was reporting some places where 1P is not working. It was not fixed for none of them. So AgileBits is not listening. For me is kind of IT suicide.

Ben

Hey @PLMan

I can appreciate your perspective here. We've come a long way with filling, but there is still room for improvement. Do you have an example of a password manager that is working with this page in its current state? In my experience most password managers intentionally avoid filling textarea fields, as doing so tends to cause more problems that it solves (i.e. things being filled where they shouldn't be).

We may be able to do better here, but QNAP has definitely decided to go in an unusual direction here which makes things difficult.

Ben

PLMan

I really doesn't understand the logic: we will fix the problem if competition will do this first. For sure it is not the way leaders go.
But answering your question: RoboForm deals with QNAP without any problems.

Ben

I really doesn't understand the logic: we will fix the problem if competition will do this first. For sure it is not the way leaders go.

To be clear: that isn't at all what I was suggesting. :)

But answering your question: RoboForm deals with QNAP without any problems.

Thanks. I'll take a look and see if I can figure out how they've approached this particular form. As I mentioned from our perspective we've tried to avoid interacting with textarea elements, as doing so tends to lead to data being filled into non-login form fields, however there may be a clever solution here.

Ben

PLMan

The clever solution is not to avoid textarea everywhere, but to customise behaviour to pages. QNAP login is not the only place. I was reporting problems with PayU payments long time ago. 1Password for years doesn't work fully because it stubbornly fills card validity date as mm/yyyy instead of mm/yy.

I really like 1Password but I simply need it to work, instead to have next bells and whistles. Manual copying of login data is really annoying.

Ben

The clever solution is not to avoid textarea everywhere, but to customise behaviour to pages.

Indeed. I've already asked our team if we could go in exactly that direction. :+1:

I really like 1Password but I simply need it to work, instead to have next bells and whistles. Manual copying of login data is really annoying.

Understandable. Thank you! I'll continue to work with our team on this.

Ben

PLMan

Time goses, Apple password filling in Safari started to deal properly with QNAP login page. 1Password still doesn't work. I'm afraid that users will die before "team" will fix the problem. Looks like main task for password manager is not managing passwords. Strange. You are forcing users to look for alternatives.

Ben

@PLMan

I'm sorry; I'm not aware of any definite plans to change this in the near future. I understand that's disappointing and that as such you may need to evaluate other solutions.

Ben

PLMan

I'm afraid that it is not only me... QNAP is one of the biggest NAS supplier worldwide. So, for sure, many 1P users are using their products.

Ben

Indeed, which makes their decision to use textarea fields on their login page all the more puzzling.

Ben

thrint

Same problem here. More of an annoyance than an actual problem as the NAS is not internet accessible and very short

ag_ana

Thank you for letting us know @thrint. I have sent your feedback to the developers too :+1:

ref: dev/core/core#2400

Unknown

This content has been removed.

ag_ana

Thank you for the suggestion @JamesHenderson! :+1: