Best development practices to ensure 1Password plugin captures user entered passwords?

Cacophone
Cacophone
Community Member
in Mac

As a user of 1Password I experience sites that seem to very nicely integrate with the 1password plugin, and some that very much don't. The most annoying thing I experience is when a "change password, old password, new password" type screen doesn't lead to the plugin successfully detecting the new password or change event and prompting me to save it -- which because I generally create 50char random passwords with 1p means I've just lost my creds & have to go back into a "forgot password" flow. Super annoying.

So as a developer building a platform to play nice with 1P plugins, does anyone have any pointers or best practices guides or whatever to guide me along as I build this?

Comments

  • Stephen_C
    Stephen_C
    Community Member

    I generally create 50char random passwords with 1p means I've just lost my creds & have to go back into a "forgot password" flow.

    Sorry this is not a direct answer to your main question—but I'm assuming your"flow" includes checking the Passwords category when that happens. That category stores generated passwords not directly linked to a saved login item in 1P so you may well find what you need there. There are other useful tips in this knowledge base article on recovering an unsaved password.

    I think AgileBits appreciates that sometimes 1P doesn't detect a password change on a site and is trying to improve the detection rate. However I just thought these tips might help in the meantime. Sorry if you already knew them.

    Stephen

  • rickfillion
    rickfillion
    edited January 2015

    Hi @Cacophone,

    I just spoke with our browser extension plugins, and they said that there's not yet a Best Practices document available to use as a reference. Here's the recommendations they gave me to pass along to you:

    • Make sure you're using a ```

    <

    form>```

    • Use field identifiers that are obvious (i.e. not auto-generated field identifiers)
    • For a password change page, make sure that there are 3 password fields
    • Aim to make your page Accessible. The same features that make a webpage accessible are what will help 1Password's extension best read the page's intention.
    • If you have any trouble, and would like to ask the developers specific questions, feel free to email support+browser@agilebits.com and they can give you a hand.

    I hope this helps.

    Rick

This discussion has been closed.