Skip to content

Server-initiated guest portal on Aruba Instant

In a server-initiated guest flow, the access point only enforces what Airgate decides. The device’s role changes from “captive portal” to “internet” because Airgate writes the portal login to the device record and asks the access point to authenticate the device again. This guide uses an Aruba Instant virtual controller (VC) and an SSID called Corp-Guest.

  1. First connection. The guest device joins Corp-Guest. The AP sends a MAC authentication request. Airgate accepts it with the captive-portal role guest-portal, which redirects web traffic to the Airgate portal.
  2. Registration. The guest registers on the portal. Optionally the password goes to a sponsor in Microsoft Teams instead of being shown.
  3. Login. After the login, Airgate:
    • sets the device’s status to Known and writes the endpoint attributes MAC-Auth Expiry and Access_Valid_Till (the end of the guest’s access);
    • sends a RADIUS CoA (re-authenticate) to the VC.
  4. Re-authentication. The AP sends a new MAC authentication request. The device now has an Access_Valid_Till in the future, so Airgate returns the internet role guest-internet.
  5. Expiry. When access ends or an administrator revokes it, Access_Valid_Till is moved to the revocation time and the device is re-authenticated. The next MAC authentication returns guest-portal again.
  • An Aruba Instant cluster with a guest VLAN, and its VC address (in this guide 192.0.2.20).
  • Your Airgate portal host name (here airgate.contoso.com) and Airgate RADIUS address (here 203.0.113.10).
  • The console certificate is from a public CA (Certificates › Server certificates › Console (HTTPS)): guests’ phones must trust the portal.
  • For sponsor delivery: a Teams workflow, see Sponsor approval in Microsoft Teams.
  1. Open Network › Switches and APs and select Add device.
  2. Name instant-vc, IP address or subnet 192.0.2.20, Vendor profile your Aruba Instant profile.
  3. On RADIUS, CoA & RadSec: enter the RADIUS shared secret, turn on RADIUS CoA / Disconnect (RFC 5176) and keep CoA port 3799.
  4. Select Add device.

With dynamic RADIUS proxy on, the VC sends all RADIUS from its own address and receives CoA there. With it off, each AP talks to Airgate directly: add the AP subnet (for example 192.0.2.0/24) as the device instead, so CoA reaches every AP.

Open Guests › Guest portal › New portal and use these settings:

Section Setting Value
General Portal name / URL slug Corp-Guest / corp-guest
General Portal type Self-registration
General Account lifetime for example 1 day; this is how long Access_Valid_Till lasts
Branding Skin a built-in skin or your own copy
Login & network Login model MAC caching + CoA
Login & network Post-login CoA Reauthenticate
Login & network Vendor handling Aruba (AOS 8 / Instant / AOS 10) or Auto-detect
Accounts & devices User name / Password E-mail address / Digits, length 6 to 8
Receipts Sponsors (Microsoft Teams) optional: on, with each host’s name and e-mail

Select Create portal and copy the Public URL, for example https://airgate.contoso.com/portal/contoso/corp-guest. The path part (/portal/contoso/corp-guest) goes into the VC.

  1. Open Access › Access policies › Add a policy › Blank.

  2. Name Guest Wi-Fi, Connection MAC authentication, Wi-Fi networks (SSID) Corp-Guest, Which devices Any device.

  3. Add the rules:

    Order Rule When Then
    1 Portal login valid Guest portal login is Still valid (Access_Valid_Till ahead) Allow, Role guest-internet
    2 Send to guest portal no condition Allow, Role guest-portal
  4. Keep Default on Deny, select Save changes, and move the policy above any catch-all policy.

The Role field sends Aruba-User-Role. The role names must match the access rules on the VC exactly.

Replace the names and addresses with your own. 203.0.113.10 is the Airgate RADIUS address; the portal host is reached on TCP 443.

wlan auth-server airgate
ip 203.0.113.10
port 1812
acctport 1813
key <RADIUS shared secret>
rfc3576
!
wlan external-captive-portal airgate-cp
server airgate.contoso.com
port 443
url "/portal/contoso/corp-guest"
auth-text "Authenticated"
server-offline-action block-user
redirect-url ""
switch-ip
!
wlan access-rule guest-portal
captive-portal external profile airgate-cp
rule any any match udp 67 68 permit
rule any any match udp 53 53 permit
rule <portal host IP> 255.255.255.255 match tcp 443 443 permit
rule any any match any any any deny
!
wlan access-rule guest-internet
rule 10.0.0.0 255.0.0.0 match any any any deny
rule 172.16.0.0 255.240.0.0 match any any any deny
rule 192.168.0.0 255.255.0.0 match any any any deny
rule any any match any any any permit
!
wlan ssid-profile Corp-Guest
essid Corp-Guest
type guest
opmode opensystem
mac-authentication
auth-server airgate
set-role-mac-auth guest-portal
captive-portal disable

Notes:

  • rfc3576 on the auth server lets the VC accept CoA from Airgate.
  • The external captive-portal profile appends mac, ip, essid, apname, vcname, switchip and url to the redirect. Airgate reads them all; mac is the device address it caches.
  • To reject forged redirect URLs, set a url-hash-key on the captive-portal profile, paste the same key into the portal’s URL hash key, and set Redirect MAC trust to Signed.
  • Guests › Guest accounts: the visitor, with the sponsor name and e-mail when sponsors are on.
  • Guests › Guest accounts › Delivery log: a Teams delivery with status sent (sponsors on).
  • Devices › Devices › the MAC › Attributes: Access_Valid_Till, Guest Username, status Known.
  • Monitor › Alerts and events, event coa.sent: the re-authenticate request answered with CoA-ACK.
  • Monitor › Sign-in log: the second MAC authentication of the device matches rule Portal login valid and returns guest-internet.
Symptom Cause Fix
The device never gets the portal The SSID does not send MAC authentication to Airgate, or the VC is not a network device. Check mac-authentication and auth-server on the SSID, and the VC under Switches and APs.
Sign-in log: No access policy handles this sign-in The policy’s SSID differs from the broadcast name. Use the exact SSID (case-sensitive).
The portal opens but shows a certificate warning The console certificate is not publicly trusted. Install a public certificate under Certificates › Server certificates.
After login the device stays in guest-portal; coa.sent shows timeout CoA does not reach the VC (port 3799, firewall, or dynamic RADIUS proxy off). Open UDP 3799 from Airgate to the VC; with dynamic RADIUS proxy off, add every AP.
coa.sent shows CoA-NAK The VC does not know the session, or the shared secret differs. Check rfc3576 and the shared secret.
Sign-in log: Denied: guest portal login check failed The device has no valid portal login and there is no rule 2. Add the catch-all rule Send to guest portal.
Portal: “Device could not be verified” The mac in the redirect had no RADIUS request in the last 15 minutes, or the URL hash is wrong. Reconnect to the SSID; check the URL hash key.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security