LastPass Extension conflicts with UiAutomation for Chromium API

Help Studio
, ,
1

I have learned that one of my extensions, LastPass, causes problems with UiPath, and I assume it’s because both are trying to use the Chromium API.

All I can say for certain is that when LastPass is on, the robot seems unable to interact with fields that the robot is trying to interact with, such as username and passwords.

When I turn the LastPass extension off, I have no problems. It’s not a huge issue because I know the solution, but it would sure be convenient if there were a way to put a step in my automations to turn off the LastPass extension if it’s on.

Is there a quick and easy way to control other extensions, or should I just use UI interactions?

1 Like
2

If you still need the LastPass, in your UiPath UI automation don’t use the ChromiumAPI interactions in your browser. But is possible, that some of your selectors to be correctly recognized only using the ChromiumAPI. So is up to you to decide what and how to use your browser automation.

3

I definitely don’t need LastPass on my robot since I pass all credentials from Orchestrator. But it’s annoying to have to turn it on and off manually when working on my dev machine, so I created a quick workflow that I published in a library so I can easily access it.

If there’s a programmatic way to turn off LastPass, that would be great, but for now this will work.

image
image1510×1590 158 KB

4

I read what you wrote again, and because of that I realized I can turn off the use of Chromium here if needed while selected on my Use Browser container:

image

I hope this is helpful to anyone who runs into the same issue!

5

Notice of Recent Security Incident in LastPass

6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.