Ir al contenido
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Iniciar sesión
  • English (US) Français Deutsch Español Türkçe
  • Abrir la demo
  • Inicio
  • Resumen COD
    Plataforma
    ResumenPlataforma: clientes y marcaFuncionesProblemas y solucionesArquitecturaDocumentationIntegracionesPrecios
    Operación y Red
    MonitoringRedNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Seguridad y Resiliencia
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomatización
    Soluciones y Más
    NIS2 & CompliancecodPassDocumentación con IA (módulo InfraScan)Abrir la demoReferenciasDescargasFAQ
  • Precios
  • Novedades
    • Blog
    • Hoja de ruta
  • FAQ
  • Sobre nosotros
    • Sobre nosotros
    • Empleo
    • Socios
    • Referencias
  • Academy
  • Contacto
COD powered by extocode GmbH
  • 0
    • Inicio
    • Resumen COD
    • Precios
    • Novedades
      • Blog
      • Hoja de ruta
    • FAQ
    • Sobre nosotros
      • Sobre nosotros
      • Empleo
      • Socios
      • Referencias
    • Academy
    • Contacto
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Iniciar sesión
  • Abrir la demo
  1. Home
  2. Documentation
  3. Modules
  4. TACACS+

TACACS+

This page describes how the included TACACS+ service is built, how you set it up and connect 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

ItemValue
PurposeAuthentication, authorisation and accounting for administrator logins on network devices. Users, groups, clients, command sets, roles, accounting
StandardTACACS+ per RFC 8907
Scope of deliveryCOD’s own TACACS+ service with its own database and its own management API, part of COD. You do not need a third-party TACACS+ server
DevicesSwitches, routers, firewalls and access servers with a TACACS+ client. MikroTik is not supported
Connections and directionDevice to the TACACS+ service. COD to the management API. The interface never talks to the API directly, always through COD
TLSTACACS+ over TLS is available and turned off by default
Credentials on the deviceAddress of the TACACS+ service and a shared secret per client
Menu“Network > TACACS+”
Firewall rulesCustomers and partners receive the list of connections and firewall rules as part of the project.

Requirements

On the device

RequirementWhy
TACACS+ client per RFC 8907MikroTik RouterOS has no TACACS+ client of its own
Address of the TACACS+ service and shared secret configuredWithout a secret the service rejects classic TACACS+
Client name in COD matches the device exactlyThe match to the client depends on the exact name
Accounting turned onThe activity probe and accounting only see devices that send accounting

In COD and on the host

  • TACACS+ module enabled for the tenant.
  • The service runs once per host and serves a single tenant.
  • The field for the module URL is only visible if NAC, Backup or Passkeepr is also enabled for the tenant.
  • Time sync via NTP on the host. See Time and DNS.

Setup

The rollout wizard in COD does not cover TACACS+. You set up the service on the host by hand.

  1. Install the packages of the TACACS+ service on the host. They are included in the cod-all package.
  2. Check the service configuration on the host.
  3. If the service runs on a separate server: by default the management API is reachable only locally. Open it for the COD server. The connection between COD and module servers belongs in a trusted network.
  4. Check the services with systemctl list-units 'cod-*'.
  5. Enable the module with the Manager account under “Admin Area > Tenant > Modules”. Then log out and log in again.
  6. Enter the address of the management API under “Location > Module URLs”. The address ends in /api/v1.
  7. Under “Network > TACACS+”, create users, user groups and clients. One shared secret per client.
  8. Under “Access Control”, create command sets, rules and roles.
  9. Set up TACACS+ on the device: address, shared secret, accounting.
  10. Use the activity probe to check whether the device speaks TACACS+.

Note: Keep a local emergency login on the device until login through TACACS+ has been tested. At remote sites: always a second access path.

Note: The service’s master key must never change after setup. Include the service configuration in your backup. You receive the complete list as part of the project.

Technical details

ItemValue
TypeAAA server for administering network devices (authentication, authorisation, accounting)
ProtocolTACACS+ per RFC 8907, optionally over TLS
AuthorisationPERMIT and DENY rules, pattern-based command authorisation through command sets, privilege levels 1 to 15 per user
RolesA role links user group, device group and rule. This gives a user different rights per device group
CryptographyArgon2id for passwords (not reversible), AES-256-GCM for sensitive fields
ManagementREST API, separate from the server service. COD talks to it through its own proxy
OperationPython, PostgreSQL
Disablingthrough an enabled flag. The service skips disabled users and rules during evaluation
Accountingsessions with user, command, device and time. Detail rows with port, remote address and privilege level. Optional live log
Diagnosisactivity probe based on the accounting data: active, inactive or no traffic
Auditchanges made through COD appear in the Admin Area audit with before and after

Activity probe

COD does not access your devices via SSH and reads no configuration. The activity probe only evaluates accounting data. A device without accounting may not appear there.

Role simulator

The simulator works out in the browser, from a role’s configuration, whether the role permits a command, denies it or has no match. It contacts nothing and changes nothing. It does not show whether the service itself agrees.

Location and rights

The connection applies per location, the rights in COD per module and location. A TACACS+ client is not bound to an asset.

Known limits

LimitWhat you can do
Single tenant, once per hostPlan a separate server for a further tenant
No MikroTikManage logins to RouterOS with RouterOS tools
The rollout wizard does not cover TACACS+Set up the service on the host by hand as described above
The module URL field is only visible if NAC, Backup or Passkeepr is also enabledIn that case, contact your partner
The management API address must end in /api/v1Check the address under “Location > Module URLs”
The client name must match exactlyWrite the name identically in COD and on the device
Without a shared secret the service rejects classic TACACS+Set a secret for each client
Without accounting the activity probe has nothing to reportTurn on accounting on the device
Direct changes to the service do not appear in the audit. The service keeps no change history of its ownChange data only through COD
The role simulator does not show the service’s decisionTest new roles on a test device
TACACS+ over TLS is off by defaultAgree on the use of TLS with your partner

Further reading

  • TACACS+ module page
  • What your network needs for TACACS+
  • Deployment shapes
  • Initial setup
  • Troubleshooting
  • Questions about the modules
  • Support: your partner is your first point of contact. Technical questions to extocode go through the helpdesk form.
← Previous: NACNext: Firewall →
Folgen Sie uns
​
  • Resumen COD
  • Funciones
  • Demo
  • Precios
  • Integraciones
  • NIS2
  • codPass
  • Referencias

Help

  • FAQ
  • Documentation
  • Descargas
  • Contacto

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

Utilizamos cookies para proporcionarle una mejor experiencia de usuario en este sitio web. Política de privacidad

Rechazar Aceptar