İçereği Atla
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Portal
  • English (US) Français Deutsch Español Türkçe
  • Demoyu açın
  • Ana Sayfa
  • COD Genel Bakış
    Platform
    Genel BakışPlatform: müşteriler ve markaÖzelliklerSorunlar ve ÇözümlerMimariDocumentationEntegrasyonlarFiyatlar
    İşletme ve Ağ
    MonitoringAğNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Güvenlik ve Dayanıklılık
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprOtomasyon
    Çözümler ve Daha Fazlası
    NIS2 & CompliancecodPassYapay zekâ ile dokümantasyon (InfraScan ek modülü)Demoyu açınReferanslarİndirilenlerSSS
  • Fiyatlar
  • Haberler
    • Blog
    • Yol Haritası
  • SSS
  • Hakkımızda
    • Hakkımızda
    • Kariyer
    • İş ortakları
    • Referanslar
  • Academy
  • İletişim
COD powered by extocode GmbH
  • 0
    • Ana Sayfa
    • COD Genel Bakış
    • Fiyatlar
    • Haberler
      • Blog
      • Yol Haritası
    • SSS
    • Hakkımızda
      • Hakkımızda
      • Kariyer
      • İş ortakları
      • Referanslar
    • Academy
    • İletişim
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Portal
  • Demoyu açın
  1. Home
  2. Documentation
  3. Modules
  4. OTP

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

PropertyValue
PurposeShared store for one-time codes of other systems, such as vendor portals, cloud consoles and device logins
MethodTime-based one-time passwords (TOTP) per RFC 6238. SHA-1, SHA-256 or SHA-512, 6 to 8 digits, 30 seconds
New tokenThrough the QR code or setup key of the other system (otpauth)
Connection and directionNo network connection of its own. COD computes the current code from the stored setup key
StorageIn COD, per location
AssignmentA token can be assigned to an asset
ScopeSeparate from the second factor of the COD sign-in
StatusPresent in COD 3.8 and not discontinued. The codes move to Passkeepr once

Requirements

RequirementWhy
OTP module enabled for the tenantNo menu entry without it
A role with the permission for the OTP module, granted with careAnyone who may read the module can reach the setup key of every token they see
Accurate time on the COD server via NTP, recommendedTOTP codes depend on the time
QR code or setup key of the other systemThe token is created from it

Time and NTP are covered on the page Time and DNS.

Setup

  1. The manager account enables the module: “Admin Area > Tenant > Modules”. Then sign out and in again.
  2. Grant the permission for the OTP module to the roles that are to use codes.
  3. Choose the location in the top bar. Tokens always belong to a location.
  4. Create groups for teams that share codes.
  5. 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.
  6. Assign the token to an asset if needed.
  7. 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

KindWho sees the token
PrivateOnly the owner. Private tokens are not in the open pool
Open pool of the locationAll users of the module at this location
GroupThe 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.

SettingWhat happens
“Only enterprise vaults” offAt unlock, the codes land in your vault “Old OTP”
“Only enterprise vaults” onPasskeepr 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

LimitWhat you can do
Read permission on the module gives access to the setup key of every visible tokenGrant the module sparingly. Use private tokens and groups
TOTP onlyManage other methods in the system concerned
Codes depend on the server timeKeep the clock of the COD server accurate via NTP
Tokens belong to exactly one locationCreate the token at the location where the team works
Not the second factor of the COD sign-inFor the COD sign-in, recovery codes and a reset by an authorised person apply
Not enabled in the open demoAsk for a personal walkthrough

Further reading

  • OTP module page
  • Passkeepr in the documentation
  • Time and DNS
  • Security
  • Troubleshooting
  • Questions about the modules
← Previous: HypervisorNext: Passkeepr →
Folgen Sie uns
​
  • COD Genel Bakış
  • Özellikler
  • Demo
  • Fiyatlar
  • Entegrasyonlar
  • NIS2
  • codPass
  • Referanslar

Help

  • SSS
  • Documentation
  • İndirilenler
  • İletişim

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

Bu web sitesinde size daha iyi bir kullanıcı deneyimi sunmak için çerezleri kullanıyoruz. Gizlilik Politikası

Reddet Kabul et