nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is Apple Watch "Accept" button causing LastPass Authenticator to disconnect?

David Jones

I am currently testing to see if this is an issue. Here's a little more information:

MacBook Pro (15-inch, 2017)

2.9 GHz Quad-Core Intel Core i7

16 GB 2133 MHz LPDDR3

macOS Monterey12.1 (21C52)

LastPass 4.86.0 (1218)

Apple Watch (1st Generation) A1554

WatchOS 4.3.2 (15U70)

iPhone 13 Pro Pro Max MLL63X/A

iOS 15.2

LastPass App 5.5.2 Built 20/12/2021, 18:25

LastPass Authenticator App LastPassMFA 2.2.2.905

Behaviour:

When signing on to the LastPass for macOS desktop App, using only the iOS App and Authenticator, everything seems to work as it should. However...

When signing in to the LastPass macOS desktop App, using my Apple Watch to authorise the login, I enter my master password and am presented with the MULTIFACTOR AUTHENTICATION window.

The app on my watch pops up and I am presented with the option to "Accept".

On pressing "Accept" I am occasionally allowed into the desktop app on my Macbook. However, almost invariably, it doesn't let me in.

So, I go to my iPhone and open the LastPass Authenticator App and I cannot see any of the 15+ MFA accounts I am normally able to see.

All I see is the "To get started, add your first account by scanning a QR code", with options to "ADD ACCOUNT" or "RESTORE FROM BACKUP".

When this happens, I have to log out of LastPass on the iPhone then go to the Authenticator App and tell it to restore from backup. This directs me to LastPass app, where I have to log in again but using SMS to avoid the fact that the Authenticator App is being stupid!

Additional troubleshooting steps:

1. Turned it off and on again, lot of times!

2. Deleted and reinstalled the iOS apps.

3. Ensured all applications and OSes are running latest versions.

069TP000001wiheYAA.png

Find more posts tagged with

Accepted answers

David Jones

In the absence of any further replies from you, @GlennD, I will finish this post with the following update.

Seems LastPass have addressed this failure in their ability to get the Authenticator and Apple Watch to work by simply enforcing that we must have both Face ID and PIN disabled in the settings of their Authenticator app, which now says:

"Apple Watch cannot be used for login verification when Face ID or PIN are enabled."

So it seems LastPass's approach to "fixing" this issue is to greatly reduce the security of their products and customers.

All comments

glenn.dobson

Hi,

With the help of some log files provided by a customer, we believe we have identified the cause of this issue and have begun working to validate that we are correct so we can release a fix.

kheiman61

Yes I have this exact same issue and it's driving me nuts. I've turned off notifications from lastpass to my apple watch because it's not only useless, it breaks my multifactor from my phone as well. Apple Watch Series 3 here.

David Jones

Thanks for the reply,@GlennD (tried to@ you but your name didn't appear in the list of users!?).

I'll mark the question as resolved once you have released the fix.

Cheers,

David.

David Jones

Hi Glen,

Additional feedback on this behaviour:

A key point in this behaviour is when in Authenticator, while it seems to have forgotten the account it should be signed into, it has a dialogue box to take you to the LastPass app. When you click on this you are taken to the LastPass app but, even though you can clearly see it is signed into your account, in the background, a dialogue box in the LastPass app states:

"Select Account Please log in to the account you want to use with LastPass Authenticator."

So, Authenticator is clearly losing it's shiz about your LastPass account, even when you are clearly currently signed in! But only when you have recently tried to "Authorize" a login to LastPass using an Apple Watch.

David Jones

Hi@"GlennD",

Just wondering if/hoping you've had some progress in the last three months? I am still seeing the issue.

Regards,

David.

David Jones

@GlennD, Are we to infer, from the radio silence, that we are no closer to a resolution for this bug?

David Jones

In the absence of any further replies from you, @GlennD, I will finish this post with the following update.

Seems LastPass have addressed this failure in their ability to get the Authenticator and Apple Watch to work by simply enforcing that we must have both Face ID and PIN disabled in the settings of their Authenticator app, which now says:

"Apple Watch cannot be used for login verification when Face ID or PIN are enabled."

So it seems LastPass's approach to "fixing" this issue is to greatly reduce the security of their products and customers.

Matthew Cooley

FWIW this is still an issue for me or it's at least related:

Face ID and PIN are turned off in the Authenticator App
Get Notification on my watch
Approve
Nothing happens
Go to Auth app on iPhone and it's like the request never happened.

If I approve though my iPhone it works fine.

chris

I have confirmed the watch based Authenticator "Accept" button only WORKS and SHOWS up if FaceID is disabled on BOTH LastPass app AND Authenticator.

If you enable FaceID on LastPass App, the accept button shows, but will NOT send an auth

If you enabled FaceID on LastPass Authenticator, the accept button does not even show.

This is so completely and insanely broken and backwards and has never seemed to get fixed Lastpass should be ashamed of themselves. This is something that should NOT escape QA on a security product that only has two apps associated with it to work.