Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -176,7 +176,8 @@
"vaults/overview",
"vaults/credentials",
"vaults/existing-credential-vault",
"vaults/fill"
"vaults/fill",
"vaults/1password"
]
},
"browsers/payments",
Expand Down
4 changes: 4 additions & 0 deletions integrations/1password.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,10 @@ icon: "/images/integration-icons/1password-logo-transparent.svg"

Connect 1Password to use credentials from your existing vaults with [Managed Auth](/auth/managed-auth). You don't need to recreate credentials in Kernel because 1Password items are discovered by domain matching.

<Note>
This page covers the service account integration for Managed Auth. For vault items where a user approves each request in the 1Password app, see [1Password Agentic Autofill](/vaults/1password).
</Note>

## How It Works

1. **Connect a service account** — Add your 1Password service account token in the dashboard
Expand Down
2 changes: 2 additions & 0 deletions snippets/collect-browser-credentials.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,7 @@ const item = await kernel.vaults.items.upsert("hn-login", {
id_or_name: vault.id,
type: "credential",
spec: {
provider: "kernel",
description: "Hacker News",
fields: [
{
Expand Down Expand Up @@ -42,6 +43,7 @@ item = kernel.vaults.items.upsert(
id_or_name=vault.id,
type="credential",
spec={
"provider": "kernel",
"description": "Hacker News",
"fields": [
{
Expand Down
Loading
Loading