Use IdP Attributes in FileWave Custom Fields
What
IdP Custom Fields bring identity attributes from an Identity Provider (IdP) into FileWave Custom Fields. FileWave 16.2 introduced this provider for Apple devices. Common sources include Okta, Google, Microsoft Entra ID (formerly Azure AD), and Keycloak.
When/Why
Use IdP Custom Fields to:
-
Dynamically populate user-specific values (e.g., email address, username, department).
-
Create Smart Groups based on IdP-sourced information.
-
Use variables in configuration profiles (e.g., pre-fill email profiles with the user’s email address).
-
Simplify large-scale deployments by automatically binding devices to users through IdP attributes.
The IdP remains the source of the attribute values, which avoids maintaining the same user data separately in FileWave.
Platform support: IdP Custom Fields are supported on macOS, iOS, and iPadOS. Windows devices do not use Enrollment Username for IdP Custom Fields in the same way they use LDAP.
How
-
Navigate to Assistants > Custom Fields > Edit Custom Field Definitions in FileWave Central.
-
Create a new field:
-
Name/Internal Name: Enter the display name and stable internal name you want to use in reports, Smart Groups, profiles, or API work.
-
Provided By: Select IdP.
-
Assigned to all devices: Select this when the field should apply across the environment; otherwise scope it to the devices that need the value.
-
-
Set the Data Type (commonly String).
-
In IdP Reference, enter the Attribute JSONPath supplied by your IdP, such as
email,displayName, ordepartment.
-
Save the Custom Field.
-
Ensure that devices are linked to users:
-
FileWave matches IdP data to a device through its Enrollment Username.
-
Set the username manually with Set Enrollment Username, collect it during ADE enrollment, or supply it through an API or import workflow.
-
Related Content
No comments to display
No comments to display