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
| Item | Value |
|---|---|
| Purpose | Authentication, authorisation and accounting for administrator logins on network devices. Users, groups, clients, command sets, roles, accounting |
| Standard | TACACS+ per RFC 8907 |
| Scope of delivery | COD’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 |
| Devices | Switches, routers, firewalls and access servers with a TACACS+ client. MikroTik is not supported |
| Connections and direction | Device to the TACACS+ service. COD to the management API. The interface never talks to the API directly, always through COD |
| TLS | TACACS+ over TLS is available and turned off by default |
| Credentials on the device | Address of the TACACS+ service and a shared secret per client |
| Menu | “Network > TACACS+” |
| Firewall rules | Customers and partners receive the list of connections and firewall rules as part of the project. |
Requirements
On the device
| Requirement | Why |
|---|---|
| TACACS+ client per RFC 8907 | MikroTik RouterOS has no TACACS+ client of its own |
| Address of the TACACS+ service and shared secret configured | Without a secret the service rejects classic TACACS+ |
| Client name in COD matches the device exactly | The match to the client depends on the exact name |
| Accounting turned on | The 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.
- Install the packages of the TACACS+ service on the host. They are included in the
cod-allpackage. - Check the service configuration on the host.
- 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.
- Check the services with
systemctl list-units 'cod-*'. - Enable the module with the Manager account under “Admin Area > Tenant > Modules”. Then log out and log in again.
- Enter the address of the management API under “Location > Module URLs”. The address ends in
/api/v1. - Under “Network > TACACS+”, create users, user groups and clients. One shared secret per client.
- Under “Access Control”, create command sets, rules and roles.
- Set up TACACS+ on the device: address, shared secret, accounting.
- 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
| Item | Value |
|---|---|
| Type | AAA server for administering network devices (authentication, authorisation, accounting) |
| Protocol | TACACS+ per RFC 8907, optionally over TLS |
| Authorisation | PERMIT and DENY rules, pattern-based command authorisation through command sets, privilege levels 1 to 15 per user |
| Roles | A role links user group, device group and rule. This gives a user different rights per device group |
| Cryptography | Argon2id for passwords (not reversible), AES-256-GCM for sensitive fields |
| Management | REST API, separate from the server service. COD talks to it through its own proxy |
| Operation | Python, PostgreSQL |
| Disabling | through an enabled flag. The service skips disabled users and rules during evaluation |
| Accounting | sessions with user, command, device and time. Detail rows with port, remote address and privilege level. Optional live log |
| Diagnosis | activity probe based on the accounting data: active, inactive or no traffic |
| Audit | changes 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
| Limit | What you can do |
|---|---|
| Single tenant, once per host | Plan a separate server for a further tenant |
| No MikroTik | Manage 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 enabled | In that case, contact your partner |
The management API address must end in /api/v1 | Check the address under “Location > Module URLs” |
| The client name must match exactly | Write 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 report | Turn on accounting on the device |
| Direct changes to the service do not appear in the audit. The service keeps no change history of its own | Change data only through COD |
| The role simulator does not show the service’s decision | Test new roles on a test device |
| TACACS+ over TLS is off by default | Agree 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.