Page MenuHomePhabricator

1Password continually triggers on focus of LDAP Search attributes field
Closed, DuplicatePublic

Description

When configuring LDAP auth, I noticed that whenever i put the cursor focus on the "Search Attributes" field, 1Password thinks that I'm submitting a password (The LDAP one entered below it I suspect) and offers to autosave it for me. Somewhat annoying.

This seems to be the only field with this kind of behavior, so I'm suspecting it has an 'alternate' implementation triggering this behavior. Perhaps it can be mitigated in some way.

Phabricator Version 302d5bcec5e761bef1397a5392d7366dbfe092fe
Arcanist Version 75cb3cf35819661d4c1abcee1e9a71c46b9cc2c8
libphutil Version 9399881fd82a432446adffa83dac0324ecf1036f

Event Timeline

hartman raised the priority of this task from to Needs Triage.
hartman updated the task description. (Show Details)
hartman added a subscriber: hartman.
epriestley triaged this task as Wishlist priority.May 22 2014, 4:04 PM
epriestley added a subscriber: epriestley.

I don't think there's anything special about the field -- I would guess that maybe 1Password has an algorithm like "if focus moves from a password field to anything which is not a one-line text field, prompt to save the password". That would let users use normal forms (which have a one-line text field called "username" or "email") but do the wrong thing in this case.

If 1Password respects "autocomplete=off" (or has some similar hint), we could conceivably add that to the password field.

This post on StackOverflow suggests it does not, though:

I use password/form managers like 1Password and RoboForm specifically to get around websites that disable autocomplete; these add-ons typically ignore the website's preferences in favor of their own more sophisticated logic.

(I also wasn't able to find anything in the 1Password docs with 30 seconds of googling "1password disable autocomplete" and similar.)

I have 1Password installed (iOS, OS X) and haven't been able to replicate this. I run it all the time.

I usually only use it in Chrome, just tested Firefox and Safari, I still can't reproduce anything. Like Evan mentioned, it's just a standard textarea.

I think this is as reasonable excuse as any to get a new Mac.