…where lcbjdhceifofjlpecfpeimnnphbcjgnc is, of course, the extension ID for https://chromewebstore.google.com/detail/xbrowsersync/lcbjdhceifofjlpecfpeimnnphbcjgnc, I have to use RegEx that instead cuts out the entire URI schema and uses the login page for a Firefox extension. However, when the login page is something like default.html, this is damn near useless, so I have to disable autofill to prevent it attempting to autofill into other extensions.
How can I consistently identify Firefox extensions? I fear I’ll have to put an FR in request that Bitwarden implement the ability to access the internal browser storage if there isn’t a method available currently.
@grb, I am able to get Bitwarden to recognize when I’m viewing a Chrome extension listed in its relevant vault entry counterpart’s URI field, but I am unable to when utilizing Firefox, due to Firefox’s apparent dependence upon installation-specific “Internal UUIDs” rather than permanent “Extension IDs” (can be a UUID, can also be an e-mail address).
Yes, but is this just for a specific Firefox extension, or do you need some way to do this automatically for a large number of Firefox extensions?
For example, to find the ID used by the Bitwarden browser extension in Firefox, you can just open the extension, then right-click in the extension window and select “View Page Source”. You can then extract the extension ID from the URL in the browser address bar.
But perhaps I’ve misunderstood what you’re looking for.