UbID user manual
This manual explains the user flows implemented in the supplied UbID Issuer, personal Vault, Wallet, and Verifier source snapshot. Button names can vary slightly by deployment, policy, or device language.
Before you begin
Use a current browser, allow pop-ups and camera access when requested, and keep access to your registered email. Biometric and passkey functions require HTTPS or localhost and a compatible browser or authenticator.
Choose the task you need
| Goal | Go to |
|---|---|
| Create and activate an UbID identity | Create an account and sign in |
| Recover or import the local secret key | Local keys, backup, and recovery |
| Enable fingerprint, Face ID, Windows Hello, or a passkey | Biometrics, passkeys, and facial enrollment |
| Store a document or obtain a credential | Documents and credentials |
| Present information to a verifier | Share credentials and solve common problems |
Understand the three main areas
- UbID Issuer and Identity Console create and maintain the identity profile, local-key protection, biometric access, facial enrollment, devices, and protected documents.
- UbID Vault or Wallet holds verifiable credentials and asks for consent before issuance or presentation.
- UbID Verifier requests evidence and applies the verification policy. A successful cryptographic verification does not by itself make a business or legal decision.
Essential security rules
- Never send your 12- or 24-word secret phrase, password, private key, backup file, or one-time code by email or chat.
- Keep at least one tested recovery method before clearing browser data, replacing a device, or deleting a local account.
- Confirm the issuer or verifier name and the requested information before continuing.
- Treat a QR code or credential-offer link like a sensitive one-time invitation. Use only one obtained from the expected institution.
- Contact the authorized UbID support channel if the displayed identity, issuer, verifier, or requested claims are unexpected.
About screenshots
The procedures are complete without screenshots. For a production publication, add validated screenshots from the target environment because operating-system prompts for passkeys, biometrics, and camera permission vary across browsers and devices.