How to designate "username" and "password" fields?
Hi,
On 1Password 4 you can view the various web form details and designate that a field be considered a username or password. This is also true on the Mac (although I don't see the word "Designation" in the UI).
I have an login entry with two fields: "changePassword" and "verifyChangePassword". The contents of the fields are different. 1Password for Mac must have created and updated the login entry a few times. 1Password 4 for Windows and 1Password 6 for Mac both show that the "changePassword" field has been designated as the password for the login. The Windows 10 Beta doesn't tell me.
I've copied the entry between vaults on Dropbox and my Family account. The entries seem identical for both kinds of vaults.
What am I missing?
Thanks in advance.
1Password Version: Beta 2016.3.200
Extension Version: Not Provided
OS Version: Windows 10
Sync Type: dropbox and family share
Comments
-
Sorry for the confusion, @bobzef!
The beta app currently does not include a control for assigning designations to web form fields. There's a bit of work left to be done with respect to editing items. We expect to flesh this out in future builds. Thanks for bringing this up!
Withut entering edit mode, though, you should be able to see which value is currently designated as the Password.
0 -
No problem with confusion; that's what betas are for :-)
I don't see any indication of which field is designated as the Password. I've attached a screen shot of what I see. I've changed the contents of the unprotected fields, but everything else is how I see it. How can I tell which field holds the current password? I've done a review of many of my passwords. They all seem to suffer some variation of having multiple fields which could be candidates for username or password. 1Password for Mac and 1Password 4 for Windows always made it possible to find the two distinguished fields that are the actual login credentials.
0 -
You're quite right, @bobzef—my data sample was too small. :blush:
A deeper investigation shows that there is no indicator of designation in the UI. I've logged the problem for tracking, so I expect we'll see a solution in a future build.
Thanks again for bringing it to our attention!
ref: rt-349
0 -
Thanks. Looking forward to a resolution.
Here's another angle on the issue. As an end user, I don't care what the web form details are. There are often so many irrelevant fields. Usually, the only things I care about are username, password, and URL. I don't even care what those fields were called in the web form. So it makes sense to initially hide the web form details and only show the useful fields labeled with their designation (rather than their names in the web form).
This does seem to be the approach taken in 1Password for Mac. 1Password 4 for Windows didn't take this approach, so it's a harder program to use. But it is survivable since the designation is shown.
My preference is that the Beta adopt the approach of 1Password for Mac rather than 1Password 4 for Windows.
0 -
@bobzef @DBrown - I wonder if this ties into the thread I created a few months ago: https://discussions.agilebits.com/discussion/comment/270067#Comment_270067
About having standardised fields in the Windows 10 Beta - I'm still hoping this is a feature that can be incorporated into the beta before it's released :+1: :chuffed:
(And I agree with bobzef - I'm really only interested in three fields when I look at my logins - URL, username & password - which, I feel, should be the highlighted ones with standardised fields).
0 -
Hi, @pbryanw!
Yes, they're part of the same "finishing touches" that still need to be made. We're all paddling like ducks, but I don't know what will or won't make it into an initial post-beta release.
Thanks for tying these threads and for holding our feet to the fire (especially so politely)!
0 -
Thanks for pointing that other thread out. It's right on the money.
0 -
Yes, indeed.
0
