The LastPass password vault extension for Chrome seems to break certain WHM functionality. For example, if I try to install an SSL certificate, and paste in the .crt, I don't get the button that appears which lets me pre-populate the rest of the fields based on the crt details... or if I go to Edit DNS and type in a domain name, it no longer automatically finds the domain name.
--snip--
Uncaught SecurityError: Blocked a frame with origin "https://www.example.com:2087" from accessing a frame with origin "chrome-extension://hdokiejnpimakedhajhdlcegeplioahd". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "chrome-extension". Protocols must match.
--snip--
I opened a ticket with LastPass, but they claim this is a WHM problem and not a LastPass problem. Below is the communication received from Last Pass:
"LastPass Ticket # 1017296: Based on the error, it looks like cPanel is trying to access our frame, rather than us trying to access their frame. So, there is nothing we can do within our product to fix it."
I opened a ticket with cPanel (ID# 4379329) and they have confirmed the incompatibility and assigned an internal case ID of #81245.
Just thought I would document this, in case anyone else came here looking for help on this problem, like I did.
- Scott
--snip--
Uncaught SecurityError: Blocked a frame with origin "https://www.example.com:2087" from accessing a frame with origin "chrome-extension://hdokiejnpimakedhajhdlcegeplioahd". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "chrome-extension". Protocols must match.
--snip--
I opened a ticket with LastPass, but they claim this is a WHM problem and not a LastPass problem. Below is the communication received from Last Pass:
"LastPass Ticket # 1017296: Based on the error, it looks like cPanel is trying to access our frame, rather than us trying to access their frame. So, there is nothing we can do within our product to fix it."
I opened a ticket with cPanel (ID# 4379329) and they have confirmed the incompatibility and assigned an internal case ID of #81245.
Just thought I would document this, in case anyone else came here looking for help on this problem, like I did.
- Scott