Use Google Workspace accounts and groups
This guide connects Airgate to Google Workspace through Google’s Secure LDAP
service (ldap.google.com). At the end, users sign in to Wi-Fi with their
Google Workspace address and password, and access rules use their Google
Groups.
What works with Google Workspace
Section titled “What works with Google Workspace”| Sign-in method | With Google Workspace |
|---|---|
| EAP-TTLS with PAP, PAP | Airgate binds to Secure LDAP as the user to check the password. |
| EAP-TLS (certificates) | Airgate looks up the user named in the certificate and reads their groups. |
| PEAP-MSCHAPv2, MS-CHAP | Not possible. Google never gives out what MS-CHAPv2 needs. Set devices to TTLS with PAP inside. |
Before you begin
Section titled “Before you begin”- A Google Workspace edition that includes Secure LDAP (for example Business Plus, Enterprise, Education Standard or Plus, Cloud Identity Premium).
- A Google Workspace super administrator.
- Airgate must reach
ldap.google.comon TCP 636.
Step 1: Add an LDAP client in Google
Section titled “Step 1: Add an LDAP client in Google”- Sign in to the Google Admin console (
https://admin.google.com). - Go to Apps › LDAP and select Add LDAP client.
- Enter LDAP client name
Airgateand an optional description, then select Continue. - Under Access permissions, set:
- Verify user credentials: Entire domain, or the organizational units whose users use Wi-Fi.
- Read user information: the same scope.
- Read group information: On.
- Select Add LDAP client.
- Select Download certificate. You get a ZIP file with a
.crt(the client certificate) and a.key(its private key). Keep the key secret. - Select Continue to client details, open Service status, set it to ON for everyone and select Save. It can take a few minutes until the client is active.
Step 2: Add the directory in Airgate
Section titled “Step 2: Add the directory in Airgate”-
Open Access › Directories and select Add directory.
-
Select Google Workspace.
-
On the General tab, enter a Name, for example
Contoso Google. -
On the Connection tab, fill in:
Field Value Primary domain contoso.com. The base DN is derived from it (dc=contoso,dc=com).LDAP client certificate (PEM) the content of the .crtfileLDAP client key (PEM) the content of the .keyfileBase DN (optional) leave empty unless you need a narrower search base -
Select Test connection, then Create source.
ldap.google.com uses a public certificate. Airgate trusts it as long as the
public CAs stay trusted for Directories under Certificates › Trusted
CAs (the default).
The default Filters & attributes search users by uid or mail and map
each group’s cn to the alias Groups.
Step 3: Check a user
Section titled “Step 3: Check a user”- Select the directory in Access › Directories and open Test user.
- Enter a user’s address, for example
alice@contoso.com. - Check that Groups lists the user’s Google Groups.
Step 4: Use the directory in an access policy
Section titled “Step 4: Use the directory in an access policy”- Open Access › Access policies and open the policy for your SSID.
- Under Allowed methods, select EAP-TTLS (and PAP if needed).
- Under Check accounts in, select Add a directory… and pick
Contoso Google. - Select Add a rule: User is in group ›
Contoso Google› the group name; Then › Allow with the VLAN. Select Done. - Select Save changes.
On the devices, use EAP-TTLS with PAP as the inner method, and trust the Airgate root CA and RADIUS server name (see Certificates and trust). On a Chromebook managed by Google, set this in the Admin console Wi-Fi network settings.
Verify
Section titled “Verify”- Open Access › Test access, choose A person signing in, enter the address and password, set Signed in with to TTLS and select Run test.
- After a real sign-in, the Monitor › Sign-in log entry shows the user, the rule and the VLAN.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Test connection: TLS or bad certificate error |
The certificate and key do not belong together, or the LDAP client is still OFF. | Paste the matching pair from the same ZIP; set Service status to ON for everyone and wait a few minutes. |
Test user: Insufficient Access Rights |
Read user information or Read group information is not granted. | Step 1.4. |
| Sign-in log: No account named “…” | The user is outside the organizational units the LDAP client may read. | Widen the scope in step 1.4. |
| Sign-in log: Wrong password | Wrong password, or Verify user credentials does not cover the user’s OU. | Check the password and the OU scope. |
| Wi-Fi fails, Test access works | The device uses PEAP. | Switch the Wi-Fi profile to TTLS with PAP. |
Related
Section titled “Related”- Okta
- Microsoft Entra ID
- Console sign-in with SSO (Google SAML for administrators)