Connector Hub

The Connector Hub is the central overview of all integrations configured for the tenant. Connectors extend Kiwire's built-in capabilities by linking it to external systems — enterprise directories for authentication, messaging gateways for OTP delivery, identity platforms for social login, and API endpoints for data sync. This page gives you a single-pane view of every connector's status, with quick access to configuration and connectivity testing.

'alt' => 'Dashboard overview', 'caption' => 'The default Kiwire dashboard layout', 'screenshot' => true, 'class' => '', ]) Drop images into: public/assets/img/docs/{page}/{filename} --}}

Image not uploaded yet public/assets/img/docs/connectors/overview.png

What Connectors Do

Without connectors, Kiwire operates in standalone mode — users authenticate against the local Kiwire user database and communications are disabled. Connectors unlock integrations for each aspect of the WiFi management workflow:

• Directory connectors (Active Directory, LDAP) — let employees log in with their existing corporate credentials instead of a separate Kiwire password.
• Identity providers (Microsoft Entra, Google OAuth, SAML 2.0, MyDigitalID) — enable social and federated login on the captive portal and enterprise enrolment flows.
• Messaging connectors (SMTP, SMS, WhatsApp) — power OTP delivery, welcome emails, voucher notifications, and security alerts.
• Hotel/PMS connector — integrates with Property Management Systems so hotel guests are automatically provisioned and billed through the front-desk system.
• API / Webhook connector — pushes user events (login, logout, registration) to external CRMs, billing platforms, or loyalty systems.

Connector Categories

Category	Connector	Primary purpose
Directory	Active Directory	Domain authentication via LDAP bind against Windows Server AD
	LDAP	Authentication against OpenLDAP, 389 Directory, FreeIPA, or any RFC 4510-compliant directory
Identity Provider	Microsoft Entra	Azure AD / Microsoft 365 OAuth2 + OIDC federated login
	Google OAuth	Google Workspace sign-in with domain restriction
	SAML 2.0	Enterprise SSO via SAML — compatible with Okta, Auth0, Ping Identity, AD FS, and others
	MyDigitalID	Malaysian national digital identity (MyDigitalID) verification
Messaging	SMTP / Email	Outgoing email for OTP, welcome messages, password resets, and security alerts
	SMS	SMS OTP delivery via a configurable HTTP SMS gateway
	WhatsApp	WhatsApp OTP and notification delivery via Meta WhatsApp Business API
Hotel / PMS	PMS Integration	Property Management System sync — room-charge billing, auto-provisioning from check-in
API	External API	HTTP webhook / API push for login, logout, and registration events
	Webhook	Outbound event hooks to third-party platforms (CRM, loyalty, billing)

Status Grid

The Connector Hub presents each connector as a card in a grid. The card shows:

• Connector name and icon — identifies the integration at a glance
• Status badge — one of three states:
  • Active (green) — configured and enabled
  • Inactive (grey) — configured but disabled
  • Not Configured (muted) — no settings have been saved yet
• Last tested — timestamp of the most recent successful connection test
• Quick actions — Configure, Test, Enable/Disable

Test Connection

Each connector has a Test button that performs a live connectivity check using the currently saved credentials:

• Active Directory / LDAP — attempts an LDAP bind with the service account credentials
• SMTP — sends a test email to a specified recipient address
• SMS / WhatsApp — sends a test message to a specified phone number
• Microsoft Entra / Google OAuth / SAML — validates the OAuth application configuration by performing a metadata discovery request
• External API — sends a test HTTP request to the configured endpoint

The test result (success or failure with error message) is shown inline and recorded as the Last Tested timestamp on the connector card.

Enable and Disable

Every connector can be toggled on or off without losing its configuration. Disabling a connector has the following effects:

• The connector no longer participates in any authentication or messaging workflow.
• Any captive portal or enterprise login method that depends on this connector will fail gracefully — users will see an appropriate error or the login method will be hidden from the portal, depending on configuration.
• The connector's configuration (credentials, endpoint URLs, mapping rules) is preserved and can be re-enabled at any time.

Navigating to Connector Details

Click a connector card (or the Configure button) to navigate to that connector's dedicated configuration page. Each connector has its own detailed settings form with fields specific to that integration type. All connector configuration pages follow the advanced configuration panel pattern — core settings are always visible, and detailed settings collapse under the Advanced Configuration section.

Connector Scope — Tenant vs Global

Most connectors are configured at the tenant level — each tenant manages its own SMTP server, AD domain, and API endpoints independently. This is the default for all connectors in the Connector Hub.