Skip to content

Use Okta accounts and groups

This guide connects Airgate to Okta. At the end, users sign in to Wi-Fi with their Okta user name and password (EAP-TTLS/PAP or PAP), certificate sign-ins are looked up in Okta, and access rules use Okta groups.

Sign-in method With Okta
EAP-TTLS with PAP, PAP Airgate checks the password with Okta’s Authentication API (/api/v1/authn).
EAP-TLS (certificates) Airgate looks up the user named in the certificate and reads their groups (needs an API token).
PEAP-MSCHAPv2, MS-CHAP Not possible. Okta does not give out what MS-CHAPv2 needs. Set devices to TTLS with PAP inside, or use certificates.

Airgate uses:

  • POST /api/v1/authn to check a password (no API token needed for this call);
  • GET /api/v1/users/{login} and GET /api/v1/users/{id}/groups with an API token (SSWS) to read the user and their groups.
  • An Okta administrator who can create API tokens. Tokens act with the permissions of the admin who creates them; a Read-Only Administrator is enough for Airgate. Use a dedicated service admin account so the token does not depend on a person.
  • Your Okta org URL, for example https://contoso.okta.com.
  • Airgate must reach the Okta org over HTTPS.
  1. In the Okta Admin Console, go to Security › API and open the Tokens tab.
  2. Select Create token, enter a name such as Airgate, and select Create token.
  3. Copy the Token value; Okta shows it only once.

Okta API tokens expire after 30 days without use. Airgate uses the token at every sign-in that needs user or group data, which keeps it active while sign-ins happen.

  1. Open Access › Directories and select Add directory.

  2. Under Cloud identity providers, select Okta.

  3. On the General tab, enter a Name, for example Contoso Okta.

  4. On the Connection tab, fill in:

    Field Value
    Okta org URL https://contoso.okta.com
    API token (SSWS) the token from step 1
    Accept password when MFA is required Off (see below)
  5. Select Test connection. With a token, Airgate calls /api/v1/users/me; without one it only checks that the org answers.

  6. Select Create source.

The default Filters & attributes map profile.login, profile.email, names, department, title and status, and each group’s profile.name to the alias Groups.

  1. Select the directory in Access › Directories and open Test user.
  2. Enter an Okta login, for example alice@contoso.com. A short name such as alice also works when it matches the part of the login before the @.
  3. Check that Groups lists the user’s Okta groups.
  1. Open Access › Access policies and open the policy for your SSID.
  2. Under Allowed methods, select EAP-TTLS (and PAP if your devices use it). Select EAP-TLS too if users have certificates.
  3. Under Check accounts in, select Add a directory… and pick Contoso Okta.
  4. Select Add a rule: User is in group › Contoso Okta › Staff; Then › Allow, VLAN 20. Select Done.
  5. Select Save changes.

On the devices, set the Wi-Fi profile to EAP-TTLS with PAP as the inner method, and trust the Airgate root CA and RADIUS server name (see Certificates and trust).

  1. Open Access › Test access, choose A person signing in, enter the login and password, set Signed in with to TTLS and select Run test. The result shows the matched rule.
  2. After a real sign-in, the entry in Monitor › Sign-in log shows the user, the policy and the rule.
Symptom Cause Fix
Test connection: okta returned HTTP 401 Wrong or revoked API token. Create a new token.
Sign-in log: No account named “…” The login does not exist in Okta (Airgate tells unknown users apart from wrong passwords with the API token). Check the user name; users type their Okta login.
Sign-in log: Wrong password, reason Okta requires MFA (MFA_REQUIRED) Okta’s sign-on policy asks for a second factor. Exempt the network sign-in from MFA in Okta, use certificates, or turn on Accept password when MFA is required.
Sign-in log: The account is disabled, reason account locked The user is locked out, suspended or deprovisioned in Okta. Unlock or reactivate the user.
Sign-in log: The account has expired, reason password expired The Okta password expired. The user changes the password in Okta.
Sign-in log: Airgate couldn’t reach the directory, reason okta HTTP 429 Okta rate limit reached. Check the org’s rate limits for /api/v1/authn and the Users API.
Groups are empty No API token, or the token’s admin cannot read groups. Add a token from an admin with read access.
Wi-Fi fails but Test access works The device uses PEAP. Set the device profile to TTLS/PAP.
© 2026 Airowire Networks Pvt. Ltd. Airgate is a product of Airowire.Product · Release notes · Security