Auto apply pass key

Is there a way to auto-apply the passkey (if there is only 1), instead of requiring to click the "Sign In" button? Would love to save myself a click.

In fact, it would be even better if it behaved like native MacOS, where instead of a click, it would ask for a touch ID.


1Password Version: 8.10.32
Extension Version: Not Provided
OS Version: MacOS 14.4.1
Browser: Chrome

Comments

  • Hello @konstk1! 👋

    Thank you for reaching out. Signing in with a passkey requires that you first confirm the sign in for two big reasons:

    1. It allows you to choose which passkey to use in a situation where you might have multiple accounts for the same website.
    2. Without user confirmation it would be possible for a website to trigger an automatic login without your consent. This can pose privacy and security implications for websites that you might want to temporarily browse anonymously without logging in right away.

    Once you see the passkey prompt from 1Password you can press Enter on your keyboard to sign in rather than having to click on the button using your mouse. 🙂

    -Dave

  • konstk1
    konstk1
    Community Member

    You'd have request sign in on the website first. I'm not suggesting auto login. I'm suggesting auto applying once the user tries to log in on the website. Frequently that requires putting in a password first.

    I think I saw the feature request elsewhere, it would be nice to trigger touch id request if there's only 1 passkey. Similar to how MacOS natively does it.

  • @konstk1

    Thanks for the reply. Pressing a sign in button, or user interaction on the website itself, isn't necessary for a website to send a WebAuthn/passkey request that requests a passkey for sign in from available password managers. Websites can send these requests invisibly. When 1Password receives a WebAuthn/passkey it will show the prompt so that you can consent to using your passkey before 1Password uses it to sign you into the website. This ensures that you're kept in the loop and aren't being signed into websites invisibly.

    Frequently that requires putting in a password first.

    Passkeys are designed to replace passwords. Are you using a passkey for two-factor authentication as an alternative to using a hardware security key? For most cases, websites that use a passkey for sign in won't require anything but a passkey.

    I think I saw the feature request elsewhere, it would be nice to trigger touch id request if there's only 1 passkey. Similar to how MacOS natively does it.

    Can you clarify this request a little more? If the goal is to speed things up then it seems like pressing the Enter key to sign in using a passkey is faster than using Touch ID.

    -Dave

  • konstk1
    konstk1
    Community Member
    edited May 17

    Are you using a passkey for two-factor authentication as an alternative to using a hardware security key? For most cases, websites that use a passkey for sign in won't require anything but a passkey.

    Many, if not most, sites still haven't replaced passwords completely and use passkey as 2FA. And those that don't, still require you to hit sign-in. For example, Google, you need to type in your email and hit submit. Or if you have multiple emails you need to chose one. If I'm doing that, ostensibly, my intent is to login. I suppose some people may not want to get auto-logged on for those services that sign you out periodically. Maybe this can be a toggle and those that want to save themselves a click, could do that.

    If the goal is to speed things up then it seems like pressing the Enter key to sign in using a passkey is faster than using Touch ID.

    Requesting touch id feels a tad more secure and makes me feel "cool" logging in with my finger print. But I can live with Enter.

    Thanks. Love the product—long time user.

  • @konstk1

    Thanks for the reply. I believe that the issue here is that a website sending a passkey request after you click on their sign in button and a website choosing to send a passkey request without any interaction from you both look the same to 1Password so we need to verify that you actually want to sign in.

    1Password asking you to confirm the sign-in is a security and privacy feature meant to protect you from being signed into a website without your explicit intention. It corresponds to 1Password's long-standing practice to always require user confirmation before filling a password into a website.

    Thanks. Love the product—long time user.

    Thank you for the kind words! 😊

    -Dave

  • konstk1
    konstk1
    Community Member

    Understood and agreed.

  • I've passed along your comments regarding Touch ID to the team. Thank you for the feedback. 🙂

    -Dave

    ref: PB-39860998

  • gorillapower
    gorillapower
    Community Member

    Hi @Dave_1P, have a question please:

    Once you see the passkey prompt from 1Password you can press Enter on your keyboard to sign in rather than having to click on the button using your mouse. 🙂

    I just installed 1Password 8 on a brand new Mac with macOS Sonoma. Pressing Enter on the keyboard to approve a Passkey sign-in does not work for me on Safari — it seems to not do anything at all. Is there a setting I need to turn on somewhere?

    Thanks very much.

  • @gorillapower

    Thanks for reaching out. In other browsers on the Mac, like Chrome, you can press enter on your keyboard when you see the sign in prompt but an issue with 1Password in Safari results in the passkey prompt not being focused automatically.

    Our developers have an internal work item open to investigate the issue further, I'm sorry for the inconvenience. For the time being, you should be able to press the tab key once after the prompt appears to focus the prompt and then press enter to complete sign in. 🙂

    -Dave

    ref: dev/core/core#24162

  • gorillapower
    gorillapower
    Community Member

    @Dave_1P Just tried, that does work. Although clicking with a mouse would be faster in this case. 😊 Thanks nevertheless.

  • @gorillapower

    Hopefully the focus issue in Safari can be fixed in a future update soon. 🙂

    -Dave

This discussion has been closed.