Skip to content

Change of Authorization

A RADIUS answer is only correct at the moment it is sent. When something changes later (a guest logs in on the portal, a certificate is revoked, an operator wants a device off the network), Airgate uses Change of Authorization (CoA, RFC 5176) to tell the switch or access point. This page explains the CoA actions, when Airgate sends them, and what the network device needs.

Action RADIUS packet Effect on the session
Reauthenticate CoA-Request The NAD re-runs authentication now. The device stays connected and receives the current policy result.
Disconnect Disconnect-Request The session ends. The device has to connect again.
Bounce port CoA-Request The switch port goes down and up (wired), so the device renews DHCP, for example after a VLAN change.
Disable port CoA-Request The switch port is shut. It stays down until it is re-enabled on the switch.
Apply CoA profile CoA-Request Push the attributes of a RADIUS_COA enforcement profile (a new role, VLAN, ACL or session timeout).

Vendors encode these actions differently. Airgate picks a template by the NAD’s vendor profile, for example Aruba AOS 8, Aruba Instant, Aruba AOS-CX, ArubaOS-Switch, Cisco IOS-XE switches, Cisco Catalyst 9800, Cisco ASA, Meraki MR and MS, Ruckus SmartZone, FortiGate, FortiSwitch, Juniper Mist and EX, Arista EOS, Extreme EXOS, ExtremeCloud IQ, H3C Comware, Ubiquiti UniFi, or the generic IETF template. A NAD without a template for an action gets a Disconnect-Request instead, or answers with a NAK.

Every CoA packet identifies the session with the values the NAD sent (calling station ID, accounting session ID, Cisco audit session ID and similar), and carries Event-Timestamp and Message-Authenticator.

Trigger Action
An operator selects Reauthenticate, Disconnect, Bounce or another action on Monitor › Connected now The chosen action.
A guest logs in on a captive portal whose login model is MAC authentication with CoA Reauthenticate, so that the next MAC authentication finds the device registered and returns the guest’s access.
A guest’s access expires and the device is still online Reauthenticate or Disconnect, depending on the guest settings, so the device goes back to the portal. Guest account expiry actions Disable and logout and Delete and logout disconnect active sessions.
A client certificate is revoked (on Certificates › Issued certificates or by revoking a BYOD device) Disconnect of the sessions that used it: by the certificate’s device MAC address, or, without one, the owner’s sessions when the owner has no other valid certificate.
A BYOD device is accepted before Airgate marked it as onboarded Reauthenticate, so that it gets the BYOD rule.
A device’s category or OS family changes, or a profile conflict is raised, and the session’s policy has profiling CoA enabled The policy’s profiler CoA profile, or Reauthenticate. Limited to once per minute and three times per hour per device.
A session breaks a session restriction (SESSION enforcement profile: concurrent sessions, time, data or expiry limit) The restriction’s configured action. With Disconnect and Block Access, the user (or the device, for a session without a user name) is also kept out until the block expires or an operator lifts it under Monitor › Connected now › Blocked.
An enforcement rule’s profiles include a RADIUS_COA profile That profile’s CoA, sent after the reply, with the profile’s delay.

Airgate does not send a CoA when you change a policy, or when a device sync brings new compliance facts. Those apply at the device’s next authentication. Use Reauthenticate on Monitor › Connected now to apply them at once.

  • To the NAD’s address (or, for a subnet entry, the NAS address the session reported if it lies in that subnet).
  • To the CoA port of the NAD (Network › Switches and APs), or the vendor’s default, else 3799. Cisco IOS defaults to 1700; most deployments configure 3799.
  • A NAD attribute CoA-Address sends CoA to another address, for example a controller’s management address.
  • For a NAD assigned to a site connector, Airgate hands the packet to the connector, which delivers it on the site network. This is how CoA reaches NADs behind NAT.

Airgate waits 3 seconds for an answer and retransmits twice. Every attempt is logged with its result (CoA-ACK, CoA-NAK, Disconnect-ACK, Disconnect-NAK, timeout or error).

  1. RADIUS CoA / Disconnect (RFC 5176) turned on for the device under Network › Switches and APs, with the right CoA port.
  2. Dynamic authorization enabled on the device itself (for example aaa server radius dynamic-author on Cisco IOS, RFC 3576 server on Aruba), accepting requests from Airgate’s address (or from the site connector) with the same shared secret.
  3. A firewall path for UDP from Airgate to the NAD on the CoA port. Behind NAT, use a site connector.

Sending CoA from the console needs the monitor:coa permission: Tenant Administrator, Network Administrator and Help Desk have it. Apply CoA profile also needs policy:read.

© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security