Change of Authorization (CoA)
Change of Authorization (CoA, RFC 5176) lets Airgate change a session that is already running: authenticate it again so a new policy result applies, disconnect it, or bounce a switch port. Guest portals, guest expiry, device profiling and helpdesk actions all depend on it. This guide enables CoA on both sides and shows how to use it.
How it works
Section titled “How it works”Airgate sends a CoA-Request or Disconnect-Request over UDP to the network device’s dynamic-authorization port, signed with the device’s RADIUS shared secret. It waits 3 seconds and retransmits twice. The device answers with an ACK (done) or a NAK with an error cause. Devices reached through a site connector receive CoA through the connector.
| Action | Packet | Effect |
|---|---|---|
| Reauthenticate | CoA-Request | The device re-runs authentication; the client stays connected and gets the current policy result. |
| Disconnect | Disconnect-Request | The session ends; the client has to reconnect. |
| Bounce port | CoA-Request | Wired: the switch flaps the port so the client renews DHCP, for example after a VLAN change. |
| Disable port | CoA-Request | Wired: the switch shuts the port. It stays down until re-enabled on the switch. |
| Apply CoA profile | CoA-Request | Pushes a RADIUS CoA enforcement profile (new role, VLAN, ACL or session timeout). |
Airgate builds the packet from a vendor template, chosen by the device’s Vendor profile (or its Vendor). When a platform has no re-authenticate or bounce packet (for example Aruba AOS 8 and Instant, Ruckus, Meraki MR, Juniper Mist, Arista), Airgate sends a Disconnect-Request instead: the client re-authenticates when it reconnects.
Before you begin
Section titled “Before you begin”- The device is added under Network › Switches and APs with a RADIUS shared secret and the right Vendor profile.
- UDP from Airgate to the device’s CoA port is allowed (3799, or 1700 on Cisco IOS).
- To send CoA from the console: an administrator role with
monitor:coa(Tenant Administrator, Network Administrator, Help Desk).
Step 1: Enable CoA in Airgate
Section titled “Step 1: Enable CoA in Airgate”- Open Network › Switches and APs and edit the device.
- On the RADIUS, CoA & RadSec tab, under Dynamic authorization (CoA), turn on RADIUS CoA / Disconnect (RFC 5176).
- Check CoA port: default
3799; Cisco IOS uses1700. The vendor profile shows its default and offers use it. - Save.
Optional device attributes, on the Groups & attributes tab:
| Attribute | Use |
|---|---|
CoA-Address |
Send CoA to this IP instead of the session’s NAS address, for example the virtual controller address of an Aruba Instant cluster. Required when the device entry is a subnet and the session’s NAS address is outside it. |
CoA-Template |
Force a vendor template, when the vendor profile does not pick the right one. |
CoA-MAC-Format |
MAC notation in the packet, when the device expects another one. |
Step 2: Enable CoA on the network device
Section titled “Step 2: Enable CoA on the network device”Use the Airgate RADIUS address (here 203.0.113.10) and the same shared
secret.
Cisco IOS-XE:
aaa server radius dynamic-author client 203.0.113.10 server-key <RADIUS shared secret> port 1700 auth-type anyAruba AOS-CX:
radius dyn-authorization enableradius dyn-authorization client 203.0.113.10 secret-key plaintext <RADIUS shared secret>Aruba Instant: add rfc3576 to the wlan auth-server of Airgate.
Aruba AOS 8 / AOS 10 gateways: add Airgate as an RFC 3576 server
(aaa rfc-3576-server 203.0.113.10 with the key) and reference it in the AAA
profile.
Other platforms call it “dynamic authorization”, “RFC 3576”, “RFC 5176” or “CoA”. Make sure the device accepts it from the Airgate address.
Step 3: Send a CoA from the console
Section titled “Step 3: Send a CoA from the console”From Monitor › Connected now:
- Find the session (search by user, MAC or switch).
- Select Reauthenticate or Disconnect in the row’s CoA column, or select several rows and choose an action at the top. Other CoA… offers Bounce port, Disable port and Apply CoA profile.
- Enter a Reason (recorded in the CoA log, the events and the audit trail) and confirm.
The same CoA menu is on a Sign-in log record and on a device (Devices › Devices › the MAC › CoA). After a change that affects authorization, the device page offers Send CoA.
The console reports how many targets acknowledged, for example “Reauthenticate: 1 of 1 targets acknowledged by the NAD”, or “no NAD acknowledged (NAK, timeout or error)”.
When Airgate sends CoA by itself
Section titled “When Airgate sends CoA by itself”| Trigger | CoA |
|---|---|
| Guest portal login (MAC caching model) | Post-login CoA of the portal (reauthenticate, bounce or disconnect) |
| Guest account expires, is disabled or deleted with a “logout” expire action | Disconnect of the guest’s sessions |
| A guest’s MAC cache lapses while online | Reauthenticate or disconnect, per Guests › Guest accounts › Defaults |
| A guest’s role changes | Reauthenticate of the guest’s cached devices |
| A device’s category or family changes, or a profile conflict is raised | Reauthenticate (or the service’s CoA profile), when profile-change CoA is on for the RADIUS service. At most one per device per minute and three per hour. |
| An access rule sends a RADIUS CoA enforcement profile | That profile, after the Accept |
| BYOD onboarding marks a device | Reauthenticate, so the new marking applies |
Verify
Section titled “Verify”- Monitor › Alerts and events, event type CoA (coa.sent): each
attempt with the device, the packet, and the result (
CoA-ACK,Disconnect-ACK,CoA-NAK,timeoutorerror). - Monitor › Sign-in log: after a reauthenticate, a new request for the same MAC appears within seconds.
Troubleshooting
Section titled “Troubleshooting”| Result or error | Cause | Fix |
|---|---|---|
RADIUS dynamic authorization (CoA) is not enabled on network device … |
The toggle is off in Airgate. | Turn on RADIUS CoA / Disconnect (RFC 5176). |
no response from … after N attempt(s): wrong shared secret, NAS unreachable / ACL, or dynamic authorization not enabled (timeout) |
The device did not answer. | Check the device’s dynamic-authorization client, the shared secret, the CoA port and the firewall. |
… refused the packet (ICMP port unreachable): dynamic authorization is not listening on that port |
Wrong CoA port. | Use 3799 or 1700 as the device expects. |
CoA-NAK (Session-Context-Not-Found) |
The device no longer has that session (client roamed or left). | Refresh Connected now; the session may already be gone. |
cannot determine the CoA address of network device … (… is a subnet entry …; set the CoA-Address attribute) |
The device entry is a subnet and the session came from an address outside it. | Set CoA-Address on the device, or add the device by its own address. |
no active session for … |
Airgate has no active session for the MAC (no RADIUS accounting from the device). | Enable RADIUS accounting on the device toward Airgate. |
network device … is disabled |
The device entry is disabled. | Enable it under Switches and APs. |