PingAM 7.5.0

Login Count Decision node

The Login Count Decision node triggers an action when a user’s successful login count property reaches a specified number.

Use the Increment Login Count node to set the login count on successful authentication.

Compatibility

Product Compatible?

PingOne Advanced Identity Cloud

Yes

PingAM (self-managed)

This functionality requires that you configure AM as part of a sample Ping Identity Platform deployment.

Yes

Ping Identity Platform (self-managed)

Yes

Inputs

This node’s Identity Attribute specifies the property it requires in the incoming node state. It uses this property to access the managed object.

Dependencies

This node depends on IDM to store the managed object.

Configuration

Property Usage

Interval

Trigger the True outcome depending on this setting, the Amount, and the login count:

AT

Proceed to True when the login count matches the Amount setting.

EVERY

Proceed to True every time the login count reaches a multiple of the Amount setting.

Default: AT

Amount

The login count to trigger a True outcome depending on the Interval.

Default: 25

Identity Attribute

The attribute used to identify the managed object in IDM.

Default: userName

Outputs

This node does not change the shared node state.

Outcomes

True

The login count reached Amount, and the Interval setting triggered this outome.

False

All other cases.

Errors

This node can throw exceptions with the following messages:

Message Notes

<Identity Attribute> not present in state

Failed to read the specified Identity Attribute in the shared node state

Failed to retrieve existing object

Failed to find the managed object using the Identity Attribute value from the shared node state

Retrieve login not found

Failed to read the managed object’s login count

Example

The following journey uses the Increment Login Count node to update the login count on successful authentication:

Incrementing login count
Determining next steps based on login count