Se rendre au contenu
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Se connecter
  • English (US) Français Deutsch Español Türkçe
  • Ouvrir la démo
  • Accueil
  • Aperçu COD
    Plateforme
    AperçuPlateforme : mandants et marqueFonctionnalitésProblèmes & solutionsArchitectureDocumentationIntégrationsTarifs
    Exploitation & Réseau
    MonitoringRéseauNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Sécurité & Résilience
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomatisation
    Solutions & Plus
    NIS2 & CompliancecodPassDocumentation par IA (module InfraScan)Ouvrir la démoRéférencesTéléchargementsFAQ
  • Tarifs
  • Actualités
    • Blog
    • Feuille de route
  • FAQ
  • À propos
    • À propos
    • Carrières
    • Partenaires
    • Références
  • Academy
  • Contact
COD powered by extocode GmbH
  • 0
    • Accueil
    • Aperçu COD
    • Tarifs
    • Actualités
      • Blog
      • Feuille de route
    • FAQ
    • À propos
      • À propos
      • Carrières
      • Partenaires
      • Références
    • Academy
    • Contact
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Se connecter
  • Ouvrir la démo
  1. Home
  2. Documentation
  3. Modules
  4. Passkeepr

Passkeepr

This page describes how Passkeepr works technically, what server and browser need for it and where the limits are.

What the module does is described on the module page.

As of: November 2026, COD 3.8.6

Documentation contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Documentation

  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Network and MikroTik
  • Automation
  • NAC
  • TACACS+
  • Firewall
  • Captive Portal
  • Monitoring
  • Backup
  • Hypervisor
  • OTP
  • Passkeepr
  • GRC
  • Inventory and CMDB import
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Overview

PropertyValue
PurposeEnd-to-end encrypted team vault for passwords, one-time codes, passkeys, cards and notes
PrincipleZero knowledge. The browser or the extension encrypts and decrypts. The server stores only ciphertext and sealed keys
CryptographyArgon2id (key derivation), X25519 (keys), AES-GCM (items)
Sign-inThrough COD. COD issues a signed token (JWT, ES384). Passkeepr verifies it with COD's signing keys (JWKS)
ReachabilityOnly through COD. Browser and extension talk to COD over HTTPS, COD forwards to Passkeepr
Data storageIts own PostgreSQL database, PostgreSQL version 18 or later
ServicePackage cod-passkeepr. Running it on the COD server is recommended
Browser extensionChrome version 137 or later as an unpacked extension, Firefox version 140 or later signed. From COD 3.8.6 at least version 3.3.6
Outbound connectionOptionally the leak check from the browser against the Pwned Passwords service. Only five characters of the hash leave the browser
SinceCOD 3.8. Passkeepr (Stronghold until 3.7) starts in COD 3.8 with an empty database

Requirements

Server

RequirementWhy
PostgreSQL version 18 or laterPasskeepr has its own database. The setup script creates it or uses an existing server
Passkeepr on the COD server, recommendedShort path, no network connection between COD and Passkeepr
On a separate server: trusted networkThe connection between COD and module servers belongs in a trusted network
HTTPS for CODMandatory for every access to COD, including the extension
Reverse proxy passes Server-Sent EventsPasskeepr uses Server-Sent Events. You receive a sample configuration as part of the project.
Time synchronisation via NTP on all hostsSee Time and DNS

Customers and partners receive the list of connections and firewall rules as part of the project.

Browser

RequirementWhy
Chrome version 137 or later, or Firefox version 140 or laterMinimum for the extension
Extension version 3.3.6 or later with COD 3.8.6COD 3.8.6 turns older versions away
Access to the Pwned Passwords service, optionalThe leak check queries from the browser, not from the server

In COD

  • Passkeepr module enabled for the tenant and rolled out for the location.
  • A role with the permission for the Passkeepr module.
  • For enterprise vaults, at least two Keepr admins. A Keepr admin is a COD administrator.

Setup

  1. The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
  2. Roll out the module: “Admin Area > Module Rollout”, module Passkeepr, choose the location, then “Install”, “Connect”, “Configure” and “Apply”. Details under Roll out modules.
  3. Grant the permission for the Passkeepr module to the roles that use the vault.
  4. Decide on the Passkeepr settings, for example “Only enterprise vaults”, “Time to move personal vaults”, “Offline copy works for” and “Auto-lock when idle”.
  5. Each person sets up Passkeepr when opening it for the first time: choose a master password, keep the Emergency Kit safe.
  6. Install the extension from Passkeepr. Open the extension dialog there. In Firefox, one click is enough. In Chrome, download the extension and choose “Load unpacked”.
  7. Create vaults. For enterprise vaults, name at least two Keepr admins.
  8. Read in existing data through the import.

Note: Keep the Emergency Kit where nobody else can read it. Never in COD and not in a backup of it.

Technical details

What the server knows

The server knowsThe server does not know
Accounts, memberships, rolesVault names, item titles, addresses, customers, passwords, notes, tags

The server holds ciphertext and sealed keys that it cannot open. Without the master password, which exists only in the browser, even a full database dump is worthless. Enterprise vaults are a deliberate exception. The organisation account can open them too. Its unlocks and changes are logged.

Sign-in

  1. The person signs in to COD.
  2. COD checks the permission for the Passkeepr module and issues a signed token.
  3. Passkeepr verifies the token with COD's signing keys.
  4. The browser unlocks the vault with the master password.

There is no second user directory. Local groups come from the location. Locking and deleting an account in COD acts on the role in the vault. Rate limiting and logging run in the service.

Kinds of vault

KindBelongs toNote
Personalone personOnly this person opens it
Sharedits membersRights “Can edit” or “Read-only”
Enterprisethe organisationStays when people leave. Two or more Keepr admins run it. The organisation account can open it

Sharing and revoking

  • You share whole vaults or single items, with people or with local groups of the location.
  • Invite links are valid for seven days and can be used once.
  • Everything is encrypted with public keys.
  • When you revoke a member's access, Passkeepr renews the vault key. The member loses access to everything stored afterwards.

Emergency Kit

PartPurpose
Recovery phrase, 24 wordsSets a new master password if you forgot yours. On the unlock page through “Forgot your master password?”
Secret KeyUnlocks Passkeepr on a new device

After a reset, Passkeepr shows a new Emergency Kit. The old one then stops working. The kit does not protect against data loss on the server.

Browser extension

FunctionNote
Fills credentialsOnly on the item's own site. A login can hold several addresses, “Match by” sets on which pages it fills
Counter on the iconShows how many items match the open page
Save after sign-inAsks whether to save the credentials
One-time codes and passkeysBelong to the item. The extension asks about passkeys in a window of its own
Cards and strong passwordsSince COD 3.8.6: cards at checkout, a strong password offered on sign-up and change-password pages
Sign-in to CODThe field type “COD sign-in” tells the extension which COD sign-in tab to fill

The extension does not create vaults, invite anyone, share anything, import anything or open the administration. That is done in Passkeepr itself. The Passkeepr service delivers the matching version of the extension.

Lock when idle

By default, the web vault locks after one hour without activity. Each person chooses 15 or 30 minutes, 1 or 2 hours or a custom time in their settings. The administrator's time under “Auto-lock when idle” is the upper limit.

History, archive and duplicates

  • Since COD 3.8.6, “History” shows the earlier versions of an item, with validity, author and difference. “Restore” brings a version back as a new version.
  • Archived items and vaults wait with their reason in the “Archived” tab. Erasing is possible only 30 days after archiving and cannot be undone.
  • Since COD 3.8.6, “Duplicates” in the admin view finds items that sit twice in a vault and moves the extra copies to the “Trash”.

Import

SourceNote
BitwardenPasskeys come along. Cards from the JSON export arrive as card items
1Password, KeePassFile import
sysPassSince COD 3.8.3 with a groups file from the sysPass database, one vault per group. Private accounts go into a vault of their owner. This needs the groups query from the COD 3.8.6 user guide
CSV, JSONFile import
  • Password-protected files can be read too.
  • On request, the import sorts the items into several vaults by the groups in the file.
  • Since COD 3.8.6, importing again with “Update existing entries” updates the items of an earlier import. Same title and user name in the same vault decide. Nothing is deleted.
  • For sysPass, “Check” first shows what would change.
  • Since COD 3.8.4, large imports run through without pausing.

There is no transfer from the former vault. With COD 3.8, every Passkeepr database starts empty.

Offline copies

Off by default. Only if an administrator allows it can chosen items be saved as one password-protected file that opens without a network. Passkeepr records who made a copy, not which items it holds.

Leak check

The browser checks passwords against the public Pwned Passwords service. It sends only five characters of a password's hash. The password itself does not leave the browser. The query comes from the browser, not from the server.

Audit

Every change is written to Passkeepr's audit log with its author. The audit appears in the Admin Area under “Audit”. A check function shows whether items are missing or were changed.

Update with a separate server

If Passkeepr runs on a host of its own, the following applies to COD 3.8.6:

  1. Update COD and Passkeepr together.
  2. The Passkeepr module reaches 3.8.6 together with COD or before COD.
  3. The Passkeepr host then delivers the new extension. Install it again in the browsers.

Agree on the order with your partner. More under Updates.

Backup

Before a database change, an update creates its own backup of the Passkeepr database. It does not replace your regular backup. Back up the database and the configuration of the service regularly. You receive the complete list as part of the project.

Known limits

LimitWhat you can do
No transfer from the former vaultEnter items again or use the import
COD 3.8.6 turns away extensions below version 3.3.6Install the extension again from Passkeepr
Chrome extension as an unpacked extensionAfter every COD update that requires a new version, install the extension again from Passkeepr
The extension does not manage vaults, sharing or importsDo that in Passkeepr itself
Passkeepr does not stop anyone from copying what they may read. What has been seen stays seenAfter someone leaves, change the credentials at the systems themselves
Offline copies and exports cannot be recalledAllow offline copies only deliberately and with a short lifetime
Against someone who can write to the database, Passkeepr protects only to a limited degreeKeep access to database and host tight
The Emergency Kit does not protect against data lossBack up the database regularly
A reverse proxy without Server-Sent Events disturbs PasskeeprLet Server-Sent Events through.
Separate server for PasskeeprRun Passkeepr on the COD server where possible. Otherwise trusted network and joint update
The leak check needs access from the browserAllow the Pwned Passwords service in the proxy if you want to use the check

Further reading

  • Passkeepr module page
  • OTP in the documentation
  • What your network needs for Passkeepr
  • Updates
  • Security
  • Roadmap with all changes in COD 3.8
  • Troubleshooting
  • Questions about the modules
← Previous: OTPNext: GRC →
Folgen Sie uns
​
  • Aperçu COD
  • Fonctionnalités
  • Demo
  • Tarifs
  • Intégrations
  • NIS2
  • codPass
  • Références

Help

  • FAQ
  • Documentation
  • Téléchargements
  • Contact

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

Nous utilisons des cookies pour vous offrir une meilleure expérience utilisateur sur ce site. Politique de confidentialité

Refuser Accepter