{"id":5396,"date":"2026-10-16T23:45:44","date_gmt":"2026-10-16T15:45:44","guid":{"rendered":"https:\/\/www.olares.com\/blog\/?p=5396"},"modified":"2026-10-16T23:45:46","modified_gmt":"2026-10-16T15:45:46","slug":"olares-credentials-explained","status":"publish","type":"post","link":"https:\/\/www.olares.com\/blog\/olares-credentials-explained\/","title":{"rendered":"Inside Olares: How your credentials work together"},"content":{"rendered":"\n

If you have used 1Password, you may already be familiar with the idea of keeping passwords in an encrypted vault. Olares also uses a vault<\/a>, but getting into it is only one part of the story. You may unlock LarePass<\/a> with a local password, sign in to Olares Desktop with another password, and use a code or phone confirmation when two-factor authentication is enabled.<\/p>\n\n\n\n

These credentials protect different things. Knowing which one you need matters when setting up a new client, signing in, or recovering access. This article shows where each credential is used, how Vault keeps saved items in sync, and what to back up before a device is lost.<\/p>\n\n\n\n

Five credentials, five roles<\/h2>\n\n\n\n

The diagram brings together five types of credentials used for identity recovery, local unlocking, Olares sign-in, second-factor verification, and host access. Each has a different role.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Where each credential is used and protected<\/figcaption><\/figure>\n\n\n\n

Mnemonic phrase<\/h3>\n\n\n\n

When you create an Olares ID<\/a> using LarePass, it generates a 12-word mnemonic phrase locally. These words can recreate the cryptographic keys that determine its decentralized identifier (DID), the underlying identifier linked to the Olares ID. Using the same phrase on another device lets you import the same identity.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
The same mnemonic phrase restores the same Olares identity<\/figcaption><\/figure>\n\n\n\n

LarePass stores the phrase encrypted locally, outside Vault, protected by the local password. The phrase also helps unlock the associated Vault data, provided that encrypted data remains available.<\/p>\n\n\n\n

Back up the phrase separately and keep it private.<\/strong> If no accessible client or backup remains, Olares cannot recreate the original phrase.<\/p>\n\n\n\n

LarePass local password<\/h3>\n\n\n\n

The local password protects the mnemonic phrase and access to Vault and other protected features within a particular LarePass client. Each client or browser extension has its own local password, which does not sync through Vault.<\/p>\n\n\n\n

Setting it gives the client a local lock after an identity has been imported. On mobile, biometric unlock can be enabled after a local password is set. It offers a convenient way to unlock protected features and can also reveal the local password after successful biometric verification.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Set a local password and use biometric verification in LarePass Mobile<\/figcaption><\/figure>\n\n\n\n

Olares login password<\/h3>\n\n\n\n

This password signs you in to Olares Desktop. LarePass may also request it when it needs to authenticate with Olares again.<\/p>\n\n\n\n

\n
\n
\"\"
Sign in to Olares Desktop<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n\n\n\n
\n
\"\"
Log in to Olares from LarePass Desktop<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n\n\n\n
\n
\"\"
Log in to Olares from LarePass Mobile<\/figcaption><\/figure>\n<\/div><\/div><\/div>\n<\/div>