Authentication nodes

LexisNexis InstantID Get Quiz node

The LexisNexis InstantID Get Quiz node calls the LexisNexis Dynamic Decision Platform (DDP) Authentication Hub to generate an IIDQA quiz based on the identity data provided to the node. This node doesn’t display anything to the end user. The node is configured with an attribute mapping to gather parameters for the API request. It sends the API request to the DDP Authentication Hub to generate a knowledge-based authentication (KBA) quiz.

The attribute source defines where the attribute mapping information is fetched at runtime:

  • User Directory: The node uses the username in shared state to query the user directory for user parameters and fulfill the attribute mapping. Typically configured in journeys where IIDQA is used for MFA, because the information for the user should be in the directory.

  • Shared State: The node inspects shared state for the user parameters to fulfill the attribute mapping. Typically configured in journeys where IIDQA is used for identity proofing for use cases such as new account origination, because the user account doesn’t yet exist.

Availability

Product Available?

PingOne Advanced Identity Cloud

Yes

PingAM (self-managed)

Yes

Ping Advanced Identity Software (self-managed)

Yes

Inputs

This node reads the following from the shared state, depending on the Attribute Source configuration:

  • username: the user’s username string. Required to resolve the desired identity when Attribute Source is User Directory.

  • objectAttributes: the user parameters for the attribute mapping. Required when Attribute Source is Shared State.

Dependencies

The node requires an integration with the LexisNexis DDP portal.

When Attribute Source is Shared State, the journey requires an interface to collect the user information and store the data in shared state.

Configuration

Property Usage

Org ID

The unique ID associated with DDP for your organization.

API Key

The unique API key generated by the DDP portal and associated with the Org ID.

Base URL

The domain URL for the DDP region where IIDQA API requests are sent. The default is the global region.

Policy

The DDP portal policy used to integrate the DDP Authentication Hub with IIDQA.

Attribute Source

Where the node inspects and gathers end user parameters to map to the attributes of the IIDQA API request. Either User Directory or Shared State.

Attribute List

A list of key-value pairs that maps user parameters to IIDQA API attributes. The key defines the IIDQA attribute, and the value defines the parameter to fetch. The fetched user parameters are based on the Attribute Source configuration. The attributes to send to IIDQA should include account_first_name, account_last_name, account_address_street1, account_address_city, account_address_state, and account_address_zip, as this provides a good probability to match a record in the LexisNexis system and generate a quiz.

Outputs

This node writes the following to the shared state:

  • iidqa.quiz: the quiz from the API response, if the get quiz operation succeeds. The LexisNexis IIDQA Quiz Collector node processes this JSON object value.

  • iidqa.request_id: the request ID associated with the DDP Authentication Hub API response. The LexisNexis IIDQA Quiz Decision node uses this value to invoke an API request with the quiz answers for validation.

  • iidqa.failure_reason: text associated with the error condition, if an error outcome is triggered.

Callbacks

This node doesn’t send any callbacks.

Outcomes

Success

The API request results in a physical match to a person based on the attribute list and a quiz is generated.

API Error

There is an issue with the API request, such as a network timeout, or the service is unavailable.

Discovery Error

A physical match to a person can’t be made based on the attribute list provided in the IIDQA API request.

Velocity Error

The IIDQA policy configured in LexisNexis triggered the outcome. Typically, the system only allows three quiz requests over a 30-minute period to prevent guessing attacks.

Error

There is an integration error. Check the debug log files for any integration issues. If the configuration looks accurate, open a support case with LexisNexis.

Errors

This node doesn’t log any error or warning messages of its own.