Device Profile Save node
Persists collected device data to a user’s profile in the identity store.
Use this node with the Device Profile Collector node to reuse the collected data in future authentications; for example, with the Device Match node and Device Location Match node.
You must establish the identity of the user before attempting to save to their profile.
A user profile can contain multiple device profiles. Use the Maximum Saved Profiles property to configure the maximum number of device profiles to persist per user. Saving a device profile with the same identifier as an existing entry overwrites the original record, and does not increment the device profile count.
In a Ping Identity Platform deployment, the end user UI displays saved device profiles to end users.
In an AM standalone deployment, the PingAM UI does not display saved device profiles to end users.
You can manage device profiles over REST, by using the /json/users/user/devices/profile endpoint for the realm.
Use the AM API Explorer for detailed information about the parameters
supported by the /devices/profile endpoint and to test it against your deployed AM instance.
In the AM admin UI, select the Help icon, and then go to API Explorer > /users > /{user} > /devices > /profile.
Compatibility
| Product | Compatible? |
|---|---|
PingOne Advanced Identity Cloud |
Yes |
PingAM (self-managed) |
Yes |
Ping Identity Platform (self-managed) |
Yes |
Properties
| Property | Usage |
|---|---|
Device Name Variable |
Specifies the name of a variable in the shared node state that contains an alias label for the device profile. |
Maximum Saved Profiles |
Specify the maximum number of device profiles to save in a user’s profile. When the maximum is reached, saving a new profile replaces the least-recently used profile. |
Save Device Metadata |
Specifies whether device metadata is saved to the user’s profile. |
Save Device Location |
Specifies whether device location metadata is saved to the user’s profile. |