WispHive Auth Documentation
Production OAuth and AAA integration documentation
This portal is the developer-facing contract for onboarding OAuth providers and AAA handoff flows with WispHive-managed captive portal authentication. It is written for production teams integrating SMEs, Educational Institutes, and ISPs.
What you can find here
Endpoint contracts
Production request and response models for hosted OAuth and AAA handoff integrations.
Provider playbooks
Concrete Google, Microsoft Entra ID, Auth0, education, and ISP integration guides.
Engineering standards
Idempotency, API key handling, error semantics, and operational practices for backend teams.
Quick reference
- API Reference
- Integration Flows
- Provider Guides
Service posture
WispHive manages the authentication entry domain and callback contracts. Your organization remains responsible for your identity provider configuration, client credentials, and user lifecycle policies such as signup, account recovery, and account suspension.
Captive portals are hosted locally on the client's own network gateway. Complete your OAuth integration first, then point your captive portal at the returned WispHive URLs.
Captive portal and OAuth in one view
A captive portal controls network access by gating users through an HTTP/HTTPS login checkpoint before granting internet access. WispHive OAuth services provide two deployment patterns for this checkpoint:
- Hosted OAuth: your captive portal redirects users to WispHive's auth domain.
- AAA handoff: your domain runs OAuth and securely hands off only derived identity data to WispHive.
Integration sequence for OAuth customers:
- Complete OAuth provider and integration setup with WispHive endpoints.
- Validate callback URLs, tokens, and redirect behavior.
- Point your captive portal at the returned WispHive login and callback URLs.
See Captive Portal Model for the full interaction model and implementation responsibilities.