OTP
This page describes how the OTP module stores one-time codes of other systems, who sees them and how they move to Passkeepr.
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
| Property | Value |
|---|---|
| Purpose | Shared store for one-time codes of other systems, such as vendor portals, cloud consoles and device logins |
| Method | Time-based one-time passwords (TOTP) per RFC 6238. SHA-1, SHA-256 or SHA-512, 6 to 8 digits, 30 seconds |
| New token | Through the QR code or setup key of the other system (otpauth) |
| Connection and direction | No network connection of its own. COD computes the current code from the stored setup key |
| Storage | In COD, per location |
| Assignment | A token can be assigned to an asset |
| Scope | Separate from the second factor of the COD sign-in |
| Status | Present in COD 3.8 and not discontinued. The codes move to Passkeepr once |
Requirements
| Requirement | Why |
|---|---|
| OTP module enabled for the tenant | No menu entry without it |
| A role with the permission for the OTP module, granted with care | Anyone who may read the module can reach the setup key of every token they see |
| Accurate time on the COD server via NTP, recommended | TOTP codes depend on the time |
| QR code or setup key of the other system | The token is created from it |
Time and NTP are covered on the page Time and DNS.
Setup
- The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
- Grant the permission for the OTP module to the roles that are to use codes.
- Choose the location in the top bar. Tokens always belong to a location.
- Create groups for teams that share codes.
- Create the token. Scan the QR code or enter the setup key. Choose whether the token is private, sits in the location's open pool or in one or more groups.
- Assign the token to an asset if needed.
- Sign in once to the other system with the code shown. This checks the token.
The copy function makes recurring entries quicker to create.
Technical details
Visibility
| Kind | Who sees the token |
|---|---|
| Private | Only the owner. Private tokens are not in the open pool |
| Open pool of the location | All users of the module at this location |
| Group | The members of the group or groups |
Anyone who may read the module can also reach the setup key of every token they see. With the setup key, the token can be recreated elsewhere.
Locations and assets
- All tokens and groups belong to a location. Switch the location in the top bar and you see a different set of tokens.
- The list has an Asset column. When the asset is moved, the token moves with it.
- Permissions apply per module and location.
Compatibility
The module works with setup keys in the common otpauth format. Any system that offers TOTP per RFC 6238 can be stored this way. The module does not support methods other than TOTP.
Separation from the COD sign-in
The second factor of the COD sign-in is a separate system within user management, with its own recovery codes. An authorised person can reset it. It has nothing to do with the OTP module. More under Security.
Move to Passkeepr
The codes of the OTP module move to Passkeepr once. How depends on the setting “Only enterprise vaults” in Passkeepr.
| Setting | What happens |
|---|---|
| “Only enterprise vaults” off | At unlock, the codes land in your vault “Old OTP” |
| “Only enterprise vaults” on | Passkeepr shows a line with “Import”. A Keepr admin creates the vaults under “Admin > Old OTP” |
Since COD 3.8.6, “Add to a login…” puts a code into a login you pick. User name, password and code then sit on one item, also in the browser extension. The OTP module stays in place afterwards.
Known limits
| Limit | What you can do |
|---|---|
| Read permission on the module gives access to the setup key of every visible token | Grant the module sparingly. Use private tokens and groups |
| TOTP only | Manage other methods in the system concerned |
| Codes depend on the server time | Keep the clock of the COD server accurate via NTP |
| Tokens belong to exactly one location | Create the token at the location where the team works |
| Not the second factor of the COD sign-in | For the COD sign-in, recovery codes and a reset by an authorised person apply |
| Not enabled in the open demo | Ask for a personal walkthrough |
Further reading
- OTP module page
- Passkeepr in the documentation
- Time and DNS
- Security
- Troubleshooting
- Questions about the modules