Quick start
This quick start takes a new Airgate tenant from empty to a first working 802.1X sign-in. At the end, a test user signs in to a Wi-Fi network through one access point, gets a VLAN, and you can see why in the Sign-in log. It takes about 30 minutes.
Before you begin
Section titled “Before you begin”- An Airgate administrator account with the Tenant Administrator or Network Administrator role. See Tenants and administrator roles.
- The address of your Airgate console, for example
https://nac.contoso.com. - One switch, wireless controller or access point you can configure, with a test SSID (for example
Corp-WiFi) or a test port. See Switches, APs and controllers for your vendor. - The address your device will use to reach Airgate (its public address, a RadSec connection or a site connector). See Add your first switch or AP.
- A test laptop or phone.
Step 1: Sign in to the console
Section titled “Step 1: Sign in to the console”- Open your console address in a browser.
- If your organisation uses single sign-on, enter your Work email and select Continue to Airgate. Otherwise select Sign in with a password instead, enter your Email or username and Password, and select Sign in.
- The console opens on Monitor › Overview. The menu on the left groups the pages into Observe, Protect & connect and Trust, with Settings at the bottom. Press
Ctrl+K(⌘+Kon a Mac) to jump to any page by name.
Step 2: Add a switch or access point
Section titled “Step 2: Add a switch or access point”- Go to Network › Switches and APs and select Add device.
- On the General tab, enter:
- Name: for example
ap-lobby-01. - IP address or subnet: the address the device sends RADIUS from, for example
10.0.0.10, or a subnet such as10.0.0.0/24for a group of APs. - Vendor profile: the device platform. It sets the RADIUS dictionary and the default CoA port.
- Name: for example
- On the RADIUS, CoA & RadSec tab:
- Enter a long, random RADIUS shared secret. You enter the same secret on the device.
- Leave Require Message-Authenticator in Access-Requests on.
- Turn on RADIUS CoA / Disconnect (RFC 5176) if the device supports it, and check the CoA port (default
3799).
- Select Add device.
- On the device itself, add Airgate as RADIUS authentication server (UDP
1812) and accounting server (UDP1813) with the same shared secret, and allow dynamic authorization from Airgate. Add your first switch or AP lists every setting.
Step 3: Add a directory, or a local test user
Section titled “Step 3: Add a directory, or a local test user”Airgate checks accounts in the directories you connect. For a first test, a local user is the quickest.
Quickest: a local user
- Go to Access › Local users and select Add user.
- Enter a Username (for example
alice), a Display name, and a Password with Confirm password. - Select Create user.
Your real directory
- Go to Access › Directories and select Add directory.
- Pick the type (for example Active Directory or Microsoft Entra ID) and fill in the connection settings.
- Select Test connection, then Create source.
See Directories for every directory type and what it can do.
Step 4: Write an access policy
Section titled “Step 4: Write an access policy”- Go to Access › Access policies and select Add a policy.
- Pick the Employees template, or Blank.
- Under Policy, set Name to
Employees. - Under Applies when:
- Connection: 802.1X.
- Wi-Fi networks (SSID):
Corp-WiFi(leave empty to match any network, wired included).
- Under Sign-in:
- Allowed methods: tick PEAP for a password test. Tick EAP-TLS as well when your devices have certificates.
- Check accounts in: select Add a directory… and pick Local users or your directory.
- Under the rules card, select Add a rule:
- Rule name:
Staff. - Leave When empty to match everyone this policy handles, or select Add condition and pick User is in group with your directory and a group.
- Then: Access Allow, Send These settings, VLAN
110. - Select Done.
- Rule name:
- Leave the Default row on Deny.
- Select Save changes. New sign-ins use the policy right away.
Write your first access policy explains each part in detail.
Step 5: Test the policy without a device
Section titled “Step 5: Test the policy without a device”- Go to Access › Test access.
- Under Who is connecting, keep A person signing in.
- Enter the Username (
alice). Enter the Password too if you want the account checked for real (this needs write access to policy, and the check is written to the audit log). - Set Signed in with to PEAP (username and password) and Wi-Fi network (SSID) to
Corp-WiFi. - Select Run test.
The Result card shows Allowed and Matched rule: Staff, with VLAN 110. Select Step-by-step details to see the full policy trace. If the result is not what you expect, fix the policy before you try a real device.
Step 6: Connect a device and watch the Sign-in log
Section titled “Step 6: Connect a device and watch the Sign-in log”- On the test laptop or phone, join
Corp-WiFiand sign in asalice. Accept the server certificate if the device asks. - In the console, go to Monitor › Sign-in log. A new row shows the user, the switch or AP, the result and the rule.
- Select the row to open the record. The tabs show the Summary, the request (Input), the reply (Output), the Computed attributes the rules saw, and the Trace.
- Go to Monitor › Connected now to see the session once the AP sends accounting.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Nothing appears in the Sign-in log | The request never reached Airgate, came from an address that is not listed, or used a wrong shared secret. | Check Monitor › Alerts and events for a Network device event. Check the device’s RADIUS server address, port and secret, and the IP address or subnet you entered. |
| No access policy handles this sign-in | No policy matches the SSID, connection type or switch. | Check Applies when on the policy, for example the SSID spelling (it must match exactly). |
| The device used a sign-in method this network doesn’t allow | The device used a method the policy does not tick. | Tick the method under Allowed methods, or fix the device’s Wi-Fi profile. |
| No account named “…” | The user is not in the directories under Check accounts in. | Check the user name and the directory list. |
| The device didn’t trust Airgate’s RADIUS certificate | The device does not trust the RADIUS server certificate. | Accept the certificate on the device, or install the Airgate root CA. See Certificates and PKI. |
The sign-in errors reference lists every reason.