Out-of-Band Authentication

Out-of-Band Authentication (OOBA) acquires authentication data from the user through a separate channel (distinct from the primary communications channel being used for the transaction). TrustX supports this type of authentication natively. Typically, the user’s mobile device (for example, smartphone or tablet) is the second channel, and the primary channel could be anything from a web site to a thick-client application running on a kiosk.

In TrustX, push notifications can be implemented to integrate an OOBA flow. TrustX supports two integration methods:

1. TrustX Push Notification - Allows a customer to initiate any TrustX Process Instance via push notification.
2. Generic Push - Allows a customer to initiate a generic push notification.

Push Notification Flow

Prerequisites

Before configuring either a TrustX or generic push notification flow, the following prerequisites must be satisfied.

1. An Identity Store must already exist. See Managing Identity Stores for more information.
2. A User must be created in the Identity Store. See Managing Users for more information.
3. An Appkey policy must be created and the Identity Store User must have a registered Appkey registered to their device. See Managing Policies and Appkey Device Registration

TrustX Push Notifications

1. Customer requests a push notification. This will happen either directly via an API on the Identity Store server, or indirectly via a TrustX Activity from a process instance. The request contains the details of the process definition & version or process definition tag, and process token parameters.
2. A limited duration Process Token is created for the push notification on the Identity Store server and provide the TrustX redirect URL as the payload for the push notification to all devices or a preferred device.
3. The user accepts the push notification on the device which redirects to the TrustX URL for the push notification process instance.
4. The 'Wait On Push Notification' activity in the original Process Instance will react to these statuses.
5. See TrustX Push Notifications for implementation instructions.

Generic Push Notifications

1. Customer requests a push notification. This will happen either directly via an API on the Identity Store server, or indirectly via a TrustX Activity from a Process Instance. The request contains the push notification contents.
2. The Identity Store server creates a push request and complete events for each device.
3. The user accepts the push notification on their device(s).
4. See Generic Push Notifications for implementation instructions.