Closed emasean closed 5 years ago
Just to clarify, when using Chrome extension's extension_id, our code works fine.
After some further checking it seems the iframe source of chrome-extension://kmendfapggjehodndflmmgagdbamhnfd/u2f-comms.html
can not be found, therefore this generic javascript error of Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('chrome-extension://kmendfapggjehodndflmmgagdbamhnfd') does not match the recipient window's origin ('null').
, on the other side, chrome-extension://pfboblefjcgdjicmnffhdgionmgcdmne/u2f-comms.html
can be found which made the Chrome extension's extension_id work.
Just wonder if everyone is using the Chrome U2F extension and not the build-in extension ID? so avoiding this issue?
Seems working now on Chrome 69.0.3497.100...
No1
we are getting the following javascript error:
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('chrome-extension://kmendfapggjehodndflmmgagdbamhnfd') does not match the recipient window's origin ('null').
when using the build-in chrome extension_id, we suspect the following code was triggered inside
u2f-api.js
:this was triggered since the origin is not whitelisted, how can we avoid this to happen?