lastpass chrome extension blocking DevTools

Question

A client uses devtools in Edge/Chrome via ctrl+shift+I but gets an error message as seen in the attached image.

This only happens with the lastpass extension enabled.

Ash C · Answer

Hi, @Maarten Flohil

I wanted to update you on this topic as we currently understand things.  TL/DR: This Chrome behavior is affecting every other app tested while in devtools working environments, and cannot be avoided right now.

Workarounds are as follows:

* Disable the LastPass extension when working in the devtools environment
* Set a never-URL preference within your LastPass vault for specific sites
* Make changes to Chrome policies:

* DeveloperToolsAvailabilityAllowlist  and put the site URLs that you allow your users to use DevTools on DeveloperToolsAvailabilityAllowlist: List of URL patterns for which Chrome DevTools are allowed to be opened | Chrome Enterprise

OR

* DeveloperToolsAvailability enabled. DeveloperToolsAvailabilityAllowlist: List of URL patterns for which Chrome DevTools are allowed to be opened | Chrome Enterprise

In managed Chrome and Edge environments, Developer Tools can be blocked when a company-installed browser extension is active. When you're logged in to LastPass, the extension injects scripts into webpages to provide features like autofill and passkeys. This is normal and required for the extension to work.

In Chrome and Edge version 149, this behavior triggers a browser policy called DeveloperToolsAvailability. If your IT team hasn't configured that policy, Developer Tools will be blocked on those pages.

This is expected behavior in managed browser environments and isn't specific to LastPass. It can affect any extension deployed through Group Policy or an MDM solution. The solution is for your IT team to configure the appropriate browser policy.

This also explains why Developer Tools works when you're logged out of LastPass or when a site is added as a Never URL. In those cases, LastPass doesn't inject scripts into the page, so the policy isn't triggered and Developer Tools remains available.

HildaC · Answer

Hello @Maarten Flohil

Thank you for bringing this issue to our attention. The problem you described has been escalated to our development team and is currently under investigation.

At this moment, we do not have an estimated time of resolution. However, please be assured that our team is prioritizing this matter and working diligently to find a solution as quickly as possible. We understand how this issue may be affecting your experience, and we sincerely apologize for any inconvenience it may cause.

Best,