Create and import local users
Airgate has a built-in user store, the Local User Repository. Use it for accounts that do not live in a company directory: lab and test accounts, service accounts for devices that sign in with a password, contractors, or a small site without AD. This guide shows how to add local users, import many at once from CSV, and let them sign in.
What works with local users
Section titled “What works with local users”Airgate stores each password as a bcrypt hash and an NT hash, so local users work with every password method:
| Sign-in method | Local users |
|---|---|
| PEAP-MSCHAPv2, MS-CHAP | Yes, when the user has an NT hash (badge NT in the list). |
| EAP-TTLS with PAP, PAP | Yes. |
| CHAP, EAP-MD5 | Only when a reversible copy is stored (badge CHAP). |
| TACACS+ (switch and router logins) | Yes; local users are always checked for admin logins. |
Before you begin
Section titled “Before you begin”- An Airgate role with identity write access (Tenant Administrator, Network Administrator or Helpdesk). Changing access policies needs Tenant Administrator or Network Administrator.
- Passwords must meet the tenant’s password policy: by default 8 to 128 characters. A stricter policy can also require mixed case, a digit or a special character.
Step 1: Add a user
Section titled “Step 1: Add a user”-
Open Access › Local users and select Add user.
-
Fill in:
Field Example Notes Username lab-printer01Case-insensitive and unique in the tenant. Display name Lab printer 01Optional. E-mail alice@contoso.comOptional. Role [Employee]Optional. Available to policies as Authorization:[Local User Repository]:Role_Name.Account enabled On Off: sign-ins fail as disabled. Change password at next login Off Account expires 2027-01-31 18:00Optional. After this time sign-ins fail as expired. Password, Confirm password Checked against the password policy. -
Optional: under Custom attributes, select Add attribute to store values such as
Department. Tick List for a multi-valued attribute (comma-separated). They are available to policies asAuthorization:[Local User Repository]:<name>. -
Select Create user. The user appears in the list with the credential badges.
To change a password later, select the key icon (Reset password) on the user’s row. Require a password change at next login is optional.
Step 2: Import users from CSV
Section titled “Step 2: Import users from CSV”- Open Access › Local users and select Import CSV.
- Select Template to download
local-users-template.csv, or prepare your own file. The first row must be a header and must containusername. - Choose Upload file (drop a file, at most 32 MB) or Paste CSV.
- Set the options:
- Existing users: Update (upsert) updates matching user names; Skip (create new only) leaves them unchanged.
- Default role: applied to rows without a role.
- Credentials of existing users (with upsert): Replace, or Keep credentials changed since the import.
- Select Validate. Airgate checks every row without saving and shows Rows, Would create, Would update, Skipped and Errors. Select Download errors for the failing rows.
- Select Import. Large files with clear-text passwords are hashed in a background job on the server; the dialog follows its progress and you can close it.
The columns (aliases in brackets):
| Column | Meaning |
|---|---|
username (user_id, userid, login, user) |
Required. |
password (user_password) |
Clear text; checked against the password policy, then hashed (bcrypt and NT). |
display_name (name, full_name, fullname, displayname) |
|
email (mail, e-mail) |
|
role (role_name, rolename) |
Role name, for example [Employee]. |
enabled (enable) |
true, false, yes, no, 1, 0. |
change_pwd_next_login (change_password) |
true or false. |
expires_at (expire_time, expiry, expires) |
RFC 3339, YYYY-MM-DD HH:MM:SS, a date or an epoch; empty clears it. |
nt_hash (password_ntlm_hash, ntlm_hash, nthash) |
32 hex characters: PEAP-MSCHAPv2 without a clear-text password. |
password_hash (legacy_hash, hash) |
A hash from another system ($pbkdf2$…, bcrypt $2…, {SSHA}…); upgraded to bcrypt at the first successful sign-in. |
legacy_hash_format (hash_format) |
Optional hint for the hash format. |
| any other column | Stored as a custom attribute of that name. |
New users need a password, an nt_hash or a password_hash. A file can
have up to 200,000 rows.
Example:
username,password,display_name,email,role,enabled,expires_at,Departmentalice,ChangeMe-2026!,Alice Example,alice@contoso.com,[Employee],true,2027-01-01 00:00:00,Financebob,An0ther-Secret!,Bob Example,bob@contoso.com,[Employee],true,,ITExport CSV on the same page exports every local user of the tenant. Credentials are never exported.
Step 3: Let local users sign in
Section titled “Step 3: Let local users sign in”- Open Access › Access policies and open the policy for the SSID or port.
- Under Allowed methods, select the methods the devices use (for example PEAP).
- Under Check accounts in, select Add a directory… and pick Local users. Order matters: Airgate checks the list from the top.
- Add rules and select Save changes.
The User is in group condition lists the directories you added under Access › Directories, not the local user repository. To give local users their own access, put them in a policy of their own (for example limited to one SSID) or allow everyone the policy handles with a rule without conditions.
Bulk changes
Section titled “Bulk changes”Select users with the checkboxes to Enable, Disable, Set role…, Set expiry… or Delete them together.
Verify
Section titled “Verify”- Open Access › Test access, choose A person signing in, enter the user name and password, set Signed in with (for example PEAP (username and password)) and select Run test.
- After a real sign-in, Monitor › Sign-in log shows the user with the
source
[Local User Repository].
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Import: CSV must have a username column |
No username header (or alias). |
Add the header row. |
Import row error: password must be at least 8 characters |
The password policy rejects the password. | Use a longer password or a hash column. |
| Sign-in log: No account named “…” | Local users are not in the policy’s Check accounts in list, or the name is wrong. | Step 3. |
| Sign-in log: Wrong password with PEAP, PAP works | The user has no NT hash (badge no NT). | Reset the password, or let the user sign in once with PAP/TTLS. |
| Sign-in log: The account is disabled | Account enabled is off. | Enable the user. |
| Sign-in log: The account has expired | Account expires has passed. | Clear or extend the expiry. |