Crate logins

Macros§

EncryptedLogin: A login stored in the database
Login: A login handed over from the store API, which has been persisted and contains persistence information such as id and time stamps
LoginCandidate: A login stored in the database, minus the encrypted fields.
LoginDb
LoginEntry: A login handed over to the store API; ie a login not yet persisted
LoginEntryWithMeta: A login together with meta fields, handed over to the store API; ie a login persisted elsewhere, useful for migrations
LoginFields
LoginMeta: Login data specific to database records
LoginStore
LoginsBridgedEngine
LoginsDeletionMetrics
LoginsSyncEngine
NSSKeyManager: Use the NSSKeyManager to use NSS for key management.
RunMaintenanceOptions
SecureLoginFields: LoginEntry fields that are stored encrypted

BulkResultEntry: A bulk insert result entry, returned by add_many and add_many_with_records Please note that although the success case is much larger than the error case, this is negligible in real life, as we expect a very small success/error ratio.
Error: Logins error type These are “internal” errors used by the implementation. This error type is never returned to the consumer.
InvalidLogin: Error::InvalidLogin subtypes
LoginOrErrorMessage
LoginsApiError

PrimaryPasswordAuthenticator: PrimaryPasswordAuthenticator is used in conjunction with NSSKeyManager to provide the primary password and the success or failure actions of the authentication process.
ValidateAndFixup

create_login_store_with_nss_keymanager
create_login_store_with_static_key_manager
create_managed_encdec
create_static_key_manager
get_registered_sync_engine: Called by the sync manager to get a sync engine via the store previously registered with the sync manager.

handle_error: A procedural macro that exposes internal errors to external errors the consuming applications should handle. It requires that the internal error implements [error_support::ErrorHandling].