Skip to main content
WiFi Pass provisions a unique personal WiFi passphrase for each registered user. Each person gets their own Identity PSK (iPSK) or MPSK provisioned directly on the WiFi controller via the vendor API — eliminating the shared password model entirely.
iPSK without RADIUS — requires a cloud API connection to the controller. Wiacom provisions credentials directly via the vendor API.iPSK with RADIUS — the RADIUS server handles per-user PSK lookup. API access to the controller is desired for initial configuration but is not required for ongoing credential management.

​
Why WiFi Pass?

Individual credentials

Every user gets their own passphrase — no sharing, no circulation

Instant revocation

Revoke a single user’s access without affecting anyone else

Credential expiry

Passphrases expire after a configurable period and are renewed on re-registration

Per-user audit trail

Every connection is tied to a known, consented registered user

​
How It Works

1

User registers

User registers through any configured onboarding channel (Guest Connect, portal, API, PMS).
2

Credential provisioned

Wiacom creates a unique iPSK on the WiFi controller via the vendor API.
3

Passphrase delivered

Passphrase is sent by email with a QR code — one tap to connect on any device.
4

User connects

User connects using standard WPA2 — no app, no profile, no special client required.
5

Lifecycle managed

Access is revocable and expiry-controlled from the Wiacom dashboard at any time.

​
Provisioning Modes

ModeBehaviour
InstantPassphrase created on registration, shown on the thank-you page and emailed immediately
ConfirmedUser clicks a confirmation link first; passphrase emailed after verification
Confirmed mode validates the email address before issuing a credential — recommended for public-facing deployments.

​
RADIUS Variant

For deployments exceeding vendor iPSK limits (e.g. 5,000 per SSID on Meraki), Wiacom supports iPSK with RADIUS mode. The SSID is configured with Wiacom RADIUS server details, and the RADIUS server performs per-user PSK lookup. Credential management remains entirely within Wiacom — the controller’s native iPSK API is not used in this path.

​
Vendor Support

WiFi Pass requires an API-connected controller. Legacy / manual mode does not support WiFi Pass.
VendorWiFi Pass support
Cisco Meraki✅ Full (up to 5,000 iPSKs per SSID; RADIUS variant for larger deployments)
ArubaComing soon
RuckusComing soon
UniFiComing soon
CambiumComing soon

​
Next Steps

Requirements

Hardware and firmware requirements by vendor

Enabling WiFi Pass

Activate and configure WiFi Pass on a location