As a User I want my FxA Synced passwords to be available in the Reference Browser

[st3fan]

This story is mostly about the synchronization part of passwords. There are separate stories about filling and management.

Tasks

• Move SyncLoginsClient functionality to services-sync-logins android-components#739 - sync-logins: Move SyncLoginsClient functionality to services-sync-logins to make it reusable
• Sync.Logins: lockStore is not thread safe android-components#762 - sync-logins: LockStore is not thread-safe.
• Protect FxA login state using the dataprotect component #121 - sync-logins: Protect FxA login state using the dataprotect component
• Integrate service-sync-logins component #200 - sync-logins: Integrate service-sync-logins component

[csadilek]

Did a first breakdown. It's mostly minor integration work to get to a first version. Bigger decision is where/how to securely store logins/passwords. Therefore, I've added #121 as a task here as well. In addition #149 is relevant, but it looks like this can be done later.

[grigoryk]

I wonder if we will be able to unify this with other syncable data. (see #206)

[mhammond]

Note that for lockbox (And thus our existing logins work), our strategy is to use sqlcipher and protect the DB encryption key - but the encrypted database itself is stored in the "usual" place. Will that work here?

[st3fan]

Looping in @bbinto to ask if this should be part of the 1st milestone.

[bbinto]

@st3fan what exactly are you asking should be part of the 1st milestone? What @mhammond mentioned? Or what Grisha suggested?