Sign in with Active Directory accounts and groups
This guide connects Airgate to Active Directory (AD). At the end, people sign in to Wi-Fi or a wired port with their AD user name and password, and access rules use their AD groups to decide the VLAN, role or ACL they get.
It is for network administrators who manage Airgate and have read access to AD.
Before you begin
Section titled “Before you begin”- A domain controller that Airgate can reach on TCP 636 (LDAPS) or TCP 389 with StartTLS. If the domain controllers are only reachable inside a site, install a site connector there (Network › Sites).
- A service account that can read users and groups. A normal domain user is
enough. Example:
svc-airgate@contoso.com. - The root certificate of the CA that issued the domain controllers’ certificates (usually your AD Certificate Services root).
- Switches or access points that use Airgate as their RADIUS server (Network › Switches and APs).
- An Airgate administrator role that can change policies (Tenant Administrator or Network Administrator).
Step 1: Export the AD root CA certificate
Section titled “Step 1: Export the AD root CA certificate”Airgate checks the domain controller’s certificate when it connects over LDAPS. AD CS roots are private, so Airgate must be told to trust yours.
On a domain-joined Windows computer, do one of the following:
- In a command prompt, run
certutil -ca.cert adroot.cer(needs the CA to be published in AD). - Open
certmgr.msc, go to Trusted Root Certification Authorities › Certificates, right-click your root CA, choose All Tasks › Export… and save it as Base-64 encoded X.509 (.CER).
Step 2: Trust the AD root CA in Airgate
Section titled “Step 2: Trust the AD root CA in Airgate”- In Airgate, open Certificates › Trusted CAs.
- Select Import CA.
- Under CA certificate, paste the PEM text or select Load file and
pick the
.cerfile. - Under Trust it for, select Directories.
- Select Import. The CA appears under Your CAs with the badge Directories.
Step 3: Add the directory
Section titled “Step 3: Add the directory”-
Open Access › Directories and select Add directory.
-
Under Directories, select Active Directory.
-
On the General tab, enter a Name, for example
Contoso AD. This is the name you pick in access policies and rules. -
On the Connection tab, fill in:
Field Example Notes Hostname dc1.contoso.comMust match a name in the domain controller’s certificate. Connection security LDAP_SSLStartTLSalso works on port 389.Nonesends passwords in clear text; do not use it.Port 636389forNoneorStartTLS.Verify server certificate On Shown when the connection security is not None.Bind DN svc-airgate@contoso.comA UPN or a full DN. Bind password the service account password Stored encrypted; never shown again. Base DN DC=contoso,DC=comWhere users and groups are searched. Search scope SubTree_SearchThe default. NetBIOS domain CONTOSOThe short domain name. Expand nested groups Off Turn on to also get the groups of groups (see step 5). -
Optional: on the Backup servers tab, select Add backup server and add a second domain controller (Hostname, Port, Security).
-
Select Test connection. A green result shows the connection time. A certificate error means step 2 is missing or the host name does not match the certificate.
-
Select Create source.
Airgate fills the Filters & attributes tab with the AD defaults: a user
search (sAMAccountName or userPrincipalName), the user’s memberOf
groups as the alias Groups (the group CN, for example Staff), and
department, title, email and UPN.
Step 4: Check a user
Section titled “Step 4: Check a user”- In Access › Directories, select the directory to open it.
- Open the Test user tab and enter a user name, for example
alice@contoso.comoralice. - The result lists the attributes AD returned. Check that Groups contains the groups you expect.
Step 5: Add the directory to an access policy
Section titled “Step 5: Add the directory to an access policy”- Open Access › Access policies.
- Open the policy that handles your secure SSID, or select Add a policy › Employees to create one.
- Under Applies when, set Connection to
802.1Xand enter the SSID in Wi-Fi networks (SSID), for exampleCorp-WiFi. Leave it empty to match any network, wired included. - Under Sign-in, in Allowed methods, select the methods your devices use: EAP-TTLS for TTLS/PAP, PEAP for PEAP-MSCHAPv2 (also needs PEAP with Active Directory), EAP-TLS for certificates.
- Under Check accounts in, open Add a directory… and select
Contoso AD. Use the arrows to put it in the order you want; Airgate checks the directories from the top. - Select Save changes at the top of the page.
Step 6: Add rules by AD group
Section titled “Step 6: Add rules by AD group”In the same policy, select Add a rule for each group. Example:
| Order | Rule name | When | Then |
|---|---|---|---|
| 1 | Staff | User is in group › Contoso AD › Staff |
Access Allow, VLAN 20 |
| 2 | Contractors | User is in group › Contoso AD › Contractors |
Access Allow, VLAN 30, ACL or firewall policy CONTRACTOR |
| Default | no rule above matches | Deny |
For each rule:
- Enter the Rule name.
- Under When, select Add condition, choose User is in group,
pick the directory, and type the group name exactly as AD shows it (the CN,
for example
Staff, not the full DN). - Under Then, choose Allow and fill in VLAN, Role, Security group tag or ACL or firewall policy as your network devices expect.
- Select Done, then Save changes.
Rules are checked from the top and the first match wins.
Verify
Section titled “Verify”- Open Access › Test access.
- Under Test, choose A person signing in, enter the Username, optionally the Password, and set Signed in with to the method you use (for example TTLS).
- Select Run test. The result shows the policy, the matched rule and what would be sent. Open Step-by-step details to see the groups AD returned.
- Connect a real device. In Monitor › Sign-in log, the entry shows the user, the policy, the rule and the VLAN. The Trace tab of the entry shows each step.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
| Test connection fails with a certificate error | The AD root CA is not trusted for Directories, or Hostname is not a name in the DC certificate. | Repeat step 2, or use the DC name that is in its certificate. |
Test connection: Invalid Credentials |
Wrong bind DN or password. | Use the UPN (svc-airgate@contoso.com) or the full DN, and re-enter the password. |
| Sign-in log: No account named “alice” | The user is not under the Base DN, or the directory is not in the policy’s Check accounts in list. | Widen the Base DN or add the directory to the policy. |
| Sign-in log: Wrong password | The password did not match. | The user re-enters it; on phones, forget the network to clear a saved password. |
| Sign-in log: The account is disabled | The account is disabled in AD. | Enable it in AD if the user should have access. |
| Sign-in log: Airgate couldn’t reach the directory | The DC did not answer in time. | Run Test connection, add a Backup server, check the firewall path on 636. |
| Sign-in log: Denied: member of group check failed | The user is not in the group the rule needs (the fact shows no groups found or the groups AD returned). |
Add the user to the group, check the group name (CN), or turn on Expand nested groups. |
| PEAP fails, TTLS works | PEAP-MSCHAPv2 needs a domain controller to check the password. | Set up PEAP with Active Directory. |