Skip to main content

FileWave Identity Provider (IdP) Integration Overview

What

Identity Provider (IdP) integration canhelps beFileWave key to meeting security requirements fromuse your InfoSecorganization's team,existing identity system for supported authentication and ease-of-useenrollment requirementsworkflows. This can reduce separate credentials for youradministrators customers.and users IdPwhile solutionskeeping allowaccess aligned with your customeridentity to have only one set of credentials, and to use them anywhere.provider.

FileWave currently supports 4Microsoft Entra ID, Okta, Google, and Keycloak IdP providers with version 15.5.x.integrations.

Only one ofconfiguration for each IdP mayprovider can be configured.active in FileWave.

When/Why

IfStart here when you currentlyalready utilizeuse an IDPIdP provider,provider you'lland want to start hereneed to understand thewhich supportedFileWave platformsworkflows can use it, which provider-specific setup article to follow, and thewhere instructionsrelated forauthentication settingor upattribute-sync access.behavior is documented.

How

LDAP Admin Integration

Known Issuelimits

At this time, FileWave IDPIdP integration isdoes limitednot replace every LDAP workflow. Use the linked IdP Custom Fields and LDAP Admin Integration articles to onlydecide FileWavewhether Admina authenticationrequirement and Apple device enrollment.  Directory data synchronization (and custom fields) between the IDP source and FileWave is not supported at this time, but willshould be addedhandled inthrough aIdP future release.  In the meantime, currentattributes, LDAP(S), synchronizationor can be used as a stop-gap to achieve the same result.both.