FileWave Identity Provider (IdP) Integration Overview

What

Identity Provider (IdP) integration helps FileWave use your organization's existing identity system for supported authentication and enrollment workflows. This can reduce separate credentials for administrators and users while keeping access aligned with your identity provider.

FileWave supports Microsoft Entra ID, Okta, Google, and Keycloak IdP integrations.

FileWave Central 16.4 opens IdP authentication in the computer’s system browser instead of an embedded frame. This requires no additional configuration and allows the provider to use browser-managed credentials and an existing browser session when organization policy permits it. See Admin Login Using an IdP Provider.

Only one configuration for each IdP provider can be active in FileWave.

When/Why

Start here when you already use an IdP provider and need to understand which FileWave workflows can use it, which provider-specific setup article to follow, and where related authentication or attribute-sync behavior is documented.

How

Use the provider-specific setup article first, then review the related articles for groups, enrollment, admin login, deployments, Smart Groups, and custom fields as needed:

• IdP Setup: Microsoft Entra AD
• IdP Setup: Okta
• IdP Setup: Google
• IdP Setup: Keycloak
• Adding IdP Groups for FileWave Authentication
• Configuring DEP Profiles for IDP Authentication
• Admin Login in Using an IdP Provider
• IdP for Deployments and Smart Groups
• IdP Custom Fields
• LDAP Admin Integration

Known limits

IdP integration does not replace every LDAP workflow. Use the linked IdP Custom Fields and LDAP Admin Integration articles to decide whether a requirement should be handled through IdP attributes, LDAP(S), or both.