Integrations

The platform is designed to work with the network and identity systems an organization already runs. It reaches those systems through standard integrations rather than through on-premises platform components. The integrations available depend on the services in use.

At a glance

Cisco

Meraki Dashboard · Catalyst / IOS-XE service gateway · Cisco ISE

Microsoft

Entra ID and Intune (EntryPoint EAP-TLS)

Federation

SAML 2.0 single sign-on

Events

Webhooks to SIEM and log management; public API for Sign In

Cisco networks

• Cisco Meraki. Integration with the Meraki Dashboard for guest network sign-in and for per-unit Wi-Fi keys. EasyPSK uses the Meraki Dashboard to provision per-unit keys on Meraki wireless.
• Cisco Catalyst and IOS-XE. Sign In can use a Cisco router as a service gateway, providing DHCP, DNS, secure tunneling, and routing integration for the captive portal.
• Cisco ISE. Endpoint Manager integrates with an existing Cisco ISE deployment through its APIs to surface and administer endpoint identity groups, without replacing ISE for authentication or authorization.

The RADIUS-based delivery of EasyPSK extends per-unit keys to Cisco Catalyst 9800 and to larger Meraki deployments: the platform acts as the SSID’s RADIUS server, over RadSec or privately through a Service Connector.

Microsoft identity

EntryPoint integrates with Microsoft Entra ID for 802.1X authentication, and with Microsoft Intune so that device compliance can be required before network access on certificate-based authentication.

Identity federation

The platform’s portals support SAML 2.0 single sign-on against common identity providers, including Microsoft Entra ID, Okta, and ADFS. Administrator access and delegated self-service access can be federated independently. See Identity and Authentication.

Events and external systems

The platform emits webhooks for configuration-audit events and for operational events, which can be delivered to external systems such as SIEM or log-management platforms. This is the supported mechanism for streaming platform activity into an organization’s own tooling. Deliveries go over the public internet by default, or privately through a Service Connector to an endpoint on the customer network. Today, a public API is available for Sign In; the other services expose webhooks for integration.

Captive-portal network signalling

For guest sign-in, the platform supports captive-portal identification through DHCP option 114 (RFC 8910) on clients that implement it, with a standard redirect fallback for clients that do not.

Related sections

• Network Requirements: the connectivity each integration needs.
• Logging, Reporting, and Retention: webhooks and audit data.