Package is of great help for understanding how it works, but it seems toīe designed solely with browser extensions in mind, and is not directly The first thing we’ll need to change is logging in with OAuth instead of It wasn’t exactly easy to figure out, it’s possible. Primary key material which is a requirement in order to decrypt the

Unrestricted access to the user account, including fetching their Which results in a “god mode” session token that gives full, Plaintext user password in order to authenticate to Firefox Accounts, In particular, we still needed access to the This approach still had room for improvement as we weren’t using theįull benefits of OAuth. The low level details of the BrowserID protocolĪnd finally its modern counterpart OAuth.īut as I explained at the end of the last article, The Firefox Accounts and Firefox Sync APIs, Thisīrought me on a long journey where I got to play with legacy clients from 8 years ago, Wanted to programmatically access my Firefox Lockwise passwords. A journey to scripting Firefox Sync / Lockwise: complete OAuth.A journey to scripting Firefox Sync / Lockwise: hybrid OAuth.A journey to scripting Firefox Sync / Lockwise: understanding BrowserID.A journey to scripting Firefox Sync / Lockwise: figuring the protocol.A journey to scripting Firefox Sync / Lockwise: existing clients.This article is part of a series about scripting Firefox Sync / Lockwise.

Firefox sync encountered an error