Device Profile Save node

The 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.

In Advanced Identity Cloud and Ping Identity Platform deployments, the end user UI displays saved device profiles to end users.

In an AM standalone deployment, the PingAM UI doesn’t display saved device profiles to end users.

You can manage device profiles over REST, using the /json/users/user/devices/profile endpoint for the realm.

Example

The following journey authenticates the user and checks whether the current device is trusted. If the device isn’t trusted yet, the journey requires an additional authentication factor and lets the user opt to trust the device:

The Page node with the Platform Username node and Platform Password node prompt the user for their credentials.
The Data Store Decision node validates the username and password.
The Device Profile Save node collects metadata about the current device.
The Device Profile Collector node compares saved device profiles with the current device.
The Inner MFA Journey, an Inner Tree Evaluator node, requires an additional authentication factor.
The Message node prompts the user with an option to trust the current device.
The Device Profile Save node saves the current device profile.
The Increment Login Count node updates the number of successful authentications.
The Progressive Profile Journey, an Inner Tree Evaluator node, invokes a journey to collect additional profile data.

Availability

Product	Available?
PingOne Advanced Identity Cloud	Yes
PingAM (self-managed)	Yes
Ping Identity Platform (self-managed)	Yes

Product

Available?

PingOne Advanced Identity Cloud

Yes

PingAM (self-managed)

Yes

Ping Identity Platform (self-managed)

Yes

Inputs

This node requires the username property in the incoming node state.

Implement a Username Collector node (standalone AM) or Platform Username node (Advanced Identity Cloud and Ping Identity Platform deployments) earlier in the journey.
This node reads the collected device metadata from the shared state.

Implement a Device Profile Collector node earlier in the journey to collect metadata for the current device.
This node can also read the device name from the incoming node state if it exists.

Dependencies

This node has no dependencies.

Configuration

Property	Usage
Device Name Variable	The name of a variable in the shared node state that contains an alias label for the device name.
Maximum Saved Profiles	The maximum number of device profiles to save in a user’s profile. Saving a device profile with the same identifier as an existing entry overwrites the original record, and doesn’t increment the device profile count. When the maximum is reached, saving a new profile replaces the least-recently used profile.
Save Device Metadata	Select this option to save device metadata to the user’s profile.
Save Device Location	Select this option to save device location metadata to the user’s profile.

Property

Usage

Device Name Variable

The name of a variable in the shared node state that contains an alias label for the device name.

Maximum Saved Profiles

The maximum number of device profiles to save in a user’s profile.

Saving a device profile with the same identifier as an existing entry overwrites the original record, and doesn’t increment the device profile count.

When the maximum is reached, saving a new profile replaces the least-recently used profile.

Save Device Metadata

Select this option to save device metadata to the user’s profile.

Save Device Location

Select this option to save device location metadata to the user’s profile.

Outputs

This node doesn’t write anything to the shared state.

Outcomes

Single outcome path.

Errors

This node doesn’t log messages of its own.

Auth node reference