Vedon Credentials

Vedon credentials — fills logins from your organisation's Vedon secret store into this browser; the automation never sees a value.

Vedon Credentials is the browser half of the Vedon platform's credential store. It lets a Vedon-managed desktop session sign in to web applications without the automation — or anyone watching it — ever seeing a password, one-time code or private key. How it works • Administrators provision credentials once, in the Vedon hub (passwords, TOTP seeds, passkeys, API tokens), scoped to tenants and agent pools and to the sites they may be used on. • When a Vedon session needs to sign in, the Vedon agent asks the hub to release a value for exactly the page that is open. The hub checks the origin, the pool, the session lease and the secret's policy, records the release in its audit trail, and the extension fills the login form (or submits it, if the secret allows). • Passkeys never leave the hub: the extension answers navigator.credentials requests by relaying the challenge to the hub, which signs it. Registration works the same way — the hub generates the key into a slot an administrator opened. • Sensitive ceremonies can require a human at the keyboard to confirm. What it does not do • It has no user interface for browsing or copying secrets — there is nothing to copy. The popup only shows whether the extension is connected to the local Vedon agent. • It stores nothing in the browser. No values, no names, no history. • It does not run without the Vedon agent installed on the machine (it connects through the browser's native messaging to the agent's in-session host), and it talks to no other server. Who it is for Organisations running Vedon-managed automation sessions (Windows and Linux desktops) that need those sessions to authenticate to web applications under central control and full audit.