CNaaS NAC provides a way for clients to authenticate themselves using IEEE 802.1X and/or MAB.
- Automatic registration of MAB clients.
- Periodic cleanup of inactive clients.
- Replication between primary and secondary server.
- API which can be used for all sorts of integrations.
- Port-locking, possible to bind clients to a single switch port for enhanced security.
- Fancy web UI written in React.
CNaaS NAC consists of two parts, NAC and NAC frontend, both runs in Docker.
We are using Docker Compose to manage all containers. First of all we want to start the CNaaS NAC containers without the frontend and a minimal YAML-file can look something like this (of course secrets and passwords should be replaced):
This will launch the containers needed for NAC. If you need to edit any configuration files for FreeRADIUS (out of the scope of this document) the easiest is to either run bash inside the nac_radius container and edit the files or do it from the host and use the directory in which nac-freeradius-data is mounted. Control socket etc for radmin is enabled inside the container for debugging.
To launch the frontend we must first have CNaaS Auth POC running, instructions available here: CNaaS Auth POC server installation. The compose file f or CNaaS NAC Front looks like this:
The three variables above should point to the URL the NAC API container exposes, the URL to the CNaaS NAC Front container and finally URL to the auth server. This works in the same way as for CNaaS NMS.