It’s Cybersecurity Awareness Month! Join our interactive training session, or learn about security and AI from 1Password experts.
 Forum Discussion
Belisarius
29 days agoNew Contributor
Lowes.com Passkey Issue
I've noticed that whenever I attempt to login to Lowes.com using passkeys, 1Password appears to be bypassed and I'm presented with the OS prompt for passkeys. I've confirmed this in Chrome and Firefox, and on Windows and Mac. Other sites seem to work fine and 1Password picks up on the passkey request.
- It appears the issue was a corrupt entry in 1Password - I recreated the Lowes.com entry and it worked fine. I've provided the corrupt entry to the 1Password team to figure out what was wrong with it - looking at the JSON, nothing jumps out as being wrong with it as compared to the new entry. Hopefully my experience can help out anyone else experiencing similar behavior. 
8 Replies
- BelisariusNew ContributorIt appears the issue was a corrupt entry in 1Password - I recreated the Lowes.com entry and it worked fine. I've provided the corrupt entry to the 1Password team to figure out what was wrong with it - looking at the JSON, nothing jumps out as being wrong with it as compared to the new entry. Hopefully my experience can help out anyone else experiencing similar behavior. - 1P_SimonHCommunity Manager Thanks for going the extra mile and helping us get to the root cause of this **and** updating everyone here, Belisarius. I'd be curious if re-creating the entry works for you, chopin1012. - chopin1012Occasional ContributorI just tried it and discovered something else. If I click "Sign In with Passkey" and am able to then click the resulting 1Password Lowe's passkey dialogue before the Mac passkey dialogue box appears, then I'm signed in using my passkey. However, if I'm unable to click the 1Password SignIn, or, what often happens, it's takes so long for the 1Password dialogue to appear that it's impossible to click SignIn before the Mac dialogue appears, then I can't sign in. Once the Mac dialogue box appears, no amount of clicking on 1Password will work. You then must start over. Sorry if this sounds confusing. I can provide a video if needed. 
 
 
- chopin1012Occasional ContributorIt's not just you. When I try to log into Lowes using Passkey, I click "Signin with Passkey". For whatever reason, the way things are on that site, as soon as the 1Password Passkey dialogue box appears, the MacOS dialogue box appears just afterward. I'm unable to interact with the 1Password box until I've dismissed the MacOS box. Unfortunately, as soon as I dismiss the MacOS box, while I can now interact with the 1Password box, the Lowes.com website moves on to logging in with a security code as soon as I dismiss the MacOS box and clicking on SignIn in the 1Password box does nothing. It seems the way the page is coded, it's impossible to signin with Passkey unless using MacOS autofill. - 1P_SimonHCommunity Manager Hi chopin1012, 
 Thanks for jumping in to confirm you're experiencing the same thing! If I could ask you to follow the same steps I outlined above and open a ticket with a diagnostic report and then share the ticket number here, I can let our Support team know you're running into the same issue to see if that helps us isolate the cause more quickly.
 
- 1P_SimonHCommunity Manager Hi Belisarius, 
 Thanks for reporting this! A coworker and I have tried to replicate the issue, but everything has been working smoothly and I couldn't find reports of this happening from other customers. So that we can investigate further, I'd like to ask you to create a diagnostics report from 1Password in your browser.
 Send a diagnostics report (browser extension)
 Attach the diagnostics to an email message addressed to support@1password.com
 With your email please include:- A link to this thread: url
- Your forum username: username
 
 You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!- BelisariusNew ContributorInteresting - I would've figured the multiple computers/different browsers would've meant it wasn't a "me" problem, but sounds like it might be! Could it be DNS related? I'm running an AdGuard DNS proxy locally - that's the only commonality I can think of. Although for the life of me I can't think of why that would cause an issue that would manifest this way. 
 Here's the Support ID number: EBS-58555-514