Generic Push Notifications

A generic push notification will send a push notification to an Identity Store User with a registered Appkey on their device. This form of push notification can be used to send information to a user.

Prerequisites

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

  1. An Appkey 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

Configure Push Notification Policy

A push notification policy is a form of Appkey Identity Store policy that can be configured for Apple Push Notifications (APN) for iOS applications or Firebase Cloud Messaging (FCM) for Android applications.

To create a new policy, follow the steps outlined below.

  1. Select the Policies page found under the Identity Stores tab in the left-side navigation menu in the Backoffice application.
  1. Using the 'Select a Store' dropdown menu, select an Appkey Identity Store. If an Identity Store that does not support Appkeys is selected, the option to create a push notification policy will be greyed out.
  1. Click the blue 'New Policy Configuration' button at the top-right of the screen. A pop-up modal will appear with a list of available policy types. Select the 'Push Notification' policy.

Push Notification Policy Configuration Options

This section will describe the various configuration options available when defining a push notification policy.

Configuration OptionDescription
Push Notification Policy NameMandatory. The name given to the push notification policy.
DescriptionOptional. An optional description for the push notification policy.
Relying Party IDMandatory. The Appkey relying party. Push notifications are only supported for device applications configured for Appkeys.
APNs Configuration
Application Bundle IDThe Bundle ID that uniquely identifies your App, for example com.daon.trustx. To avoid conflicts, Apple encourages developers to use reverse domain name notation for choosing an application's bundle identifier. Must contain only alphanumeric characters (A–Z, a–z, and 0–9), hyphens (-), and periods (.)
Team IDThe issuer key, the value for which is the 10-Character Team ID you use for developing your company apps. Obtain this value from your developer.apple.com account.
Use SandboxOptional. Enable APN sandbox environment.
Sound EnabledOptional. Whether to enable ping sound when notification is sent.
FCM Configuration
FCM URLThe FCM URL - available from https://fcm.googleapis.com/v1/projects/my_project_id/messages:send

APN Configuration

To configure iOS push notifications, you’ll need four pieces of information from your Apple Developer account.

  1. Application Bundle ID

    1. Go to https://developer.apple.com/account/resources/identifiers/list.
    2. Under Identifiers, find your app.
    3. Copy the Bundle ID (e.g., com.yourcompany.yourapp).
  2. Team ID

    1. Log in to https://developer.apple.com/account/.
    2. Click [Account Name] → Membership Details. in the top-right corner.
    3. Copy the Team ID listed there.
  3. Key ID

    1. In your Apple Developer account, navigate to Certificates, Identifiers & Profiles → Keys
    2. Create a new key (or select an existing one) and enable Apple Push Notifications service (APNs).
    3. After creating the key, copy the Key ID.
  4. Token Signing Key

    1. When you create the key, download the .p8 file immediately (Apple only allows one download).
    2. Open the .p8 file in a text editor.
    3. Copy the entire content (including -----BEGIN PRIVATE KEY----- and -----END PRIVATE KEY-----) and paste it into the Token Signing Key field.
  • You must have an Apple Developer Program membership.
  • Keep your .p8 file secure—Apple does not allow re-downloading.
  • If you lose the file, you will need to create a new key.

FCM Configuration

To configure Android push notifications, you’ll need two pieces of information from your Firebase project.

  1. FCM URL

    1. Go to https://console.firebase.google.com/.
    2. Select your project.
    3. Navigate to Project Settings → Cloud Messaging.
    4. Copy the FCM endpoint URL (usually https://fcm.googleapis.com/fcm/send).
    5. Paste it into the FCM URL field.
  2. Google Application Credentials

    1. In the same Cloud Messaging section, click Manage Service Accounts or go to https://console.cloud.google.com/.
    2. Create a Service Account for your Firebase project if one does not exist.
    3. Generate a JSON key for the service account.
    4. Open the downloaded .json file in a text editor.
    5. Copy the entire JSON content and paste it into the Google Application Credentials field.
  • You must have a Firebase project linked to your Android app.
  • Keep your service account JSON secure—do not share it publicly.
  • If compromised, revoke the key and generate a new one.

Configure the Process Definition

This section will describe the steps necessary for configuring a standard Process Definition that integrates a TrustX push notification flow.

A typical Process Definition will follow the structure:

  1. Get an Identity Store User.
  2. Initiate a generic push notification.
  3. Conclude Process Instance.

The Process Definition outlined above will be implemented in this section of the guide.

Create a New Process Definition

  1. Create a new Process Definition by navigating to the Process Definitions page found in the left-side navigation bar of the Backoffice application.
  2. On the top-right of the Process Definition page, click the 'New Process Definition' button.
  3. Create a new Process Definition by clicking the 'New Process Definition' option.

Configure Process Definition

  1. Add a 'Start' event at the beginning of the Process Designer.
  2. Connect a 'Get User' activity to the 'Start' event. This will be used to retrieve information about the the Identity Store User who will be sent a push notification.
  1. The 'Get User' activity supports the following input parameters.
Parameter Description Type Default
Store Name Required - Represents the Identity Store that the User belongs to. String
User External ID The External ID of the User to be returned. String
User ID The ID of the User to be returned. String
User Key The User Key of the User to be returned. String user1
  1. Add a 'Generic Push Notification' activity to the Process Designer and connect it to the 'Get User' activity using the global connect tool.
  1. The 'Generic Push Notification' activity supports the following activities.
Parameter Description Type Default
localised Message Arguments Optional list of strings to be inserted into the localised message. Either a title/message or a localised title/message must be supplied, not both or neither. List[String]
localised Message Key Optional. Reference to a localised title in the device application. String
localised Title Arguments Optional list of strings to be inserted into the localised title. List[String]
localised Title Key Optional. Reference to a localised title in the device application. String
Message Optional. Message to be displayed. String
Push Notification Parameters Optional map of strings supplied in the push notification to the device application. List[String]
Relying Party ID The Appkey relying party which references the customer application to which the push notification(s) will be sent. String
Retry Hint Duration (Seconds) Optional. Default value of 60 and a maximum allowed value of 1000. A value of 0 or less indicates that retries are disabled. Indicates for how long to retry sending the push if the service is down or busy. Integer ${60}
Store Name Mandatory. The Identity Store containing the user String
Time To Live (Seconds) Mandatory. Time to live of the push notification in seconds. Minimum valid value of 60 and a maximum of 2419200 (28 days). Integer
Title Optional. Title to be displayed. String
User External ID Optional. External (customer) ID of the user. String
User ID Optional. Internal ID of the user. String
User Key Optional. TrustX reference key for the user. String
  1. The activity also includes the following error boundary events.
Error EventDescription
No Valid Destinations AvailableThis error can occur if the push notification expires.
No Destinations AvailableThis error is triggered when no Appkey is found registered to the specified User and device.
Other ErrorThis error can trigger if any other error besides those listed above occurs.

It is also possible to send a generic push notification via API using the example query:

Permissions: TNT#{tenant}#IdentityStore:sendPushNotification

Example:

HTTP
Copy
  1. Add a 'Simple Decider' to the Process Definition and connect each of the boundary events to the activity. This activity will determine the final outcome of the Process Instance.
  1. Once the Process Definition has been configured, click the 'Save & Deploy' button.

Test and View Results

To test the Process Definition, create a new Process Token by navigating to the Process Definitions > Process Tokens page in the Backoffice application.

  1. On the Process Tokens landing page, click the 'New Process Token' button.
  2. A popup modal will appear where details of the Process Token can be entered.
  3. Once the push notification is sent, a wait screen with be presented to the user in the Trust Web application.

Viewing Push Notifications Per User

Active push notifications associated with an IDS User can be viewed from the Users page in the Backoffice.

  1. From the Backoffice application, navigate to Identity Store > Users.
  1. Using the filter options available, chose the Identity Store and optional ID to find the desired IDS User.
  2. Activity Push Notifications will be listed under the Active Push Notifications section.
  1. This section will include the following information.
TitleDescription
Push TypeThe type of push notification. Options can be TRUSTX or GENERIC.
Date CreatedThe date the push notification was originally created.
Process Instance IDThe ID of the child Process Instance that was initiated via the push notification. This is only applicable for the TrustX push notification type.
Process Instance StatusThe current status of the Process Instance.
  1. Selecting the magnifying glass under the 'Actions' column will expand to provide more details on the push notification.

Push Notification Details

The Push Notification Details page displays a list of details relating to a specific push notification.

Included in this page is the following information.

TitleDescription
Relying Party IDThe ID of the relying party.
TypeThe push notification type. Options can be TRUSTX or GENERIC.
Created AtThe date the push notification was created.
Expires AtThe date and time in which the push notification will expire.
TitleThe title of the push notification.
MessageThe message of the push notification.
Title KeyReference to a title in the device application.
Title ArgumentsOptional list of strings inserted into the title.
Message KeyReference to a message in the device application.
Message ArgumentsOptional list of strings inserted into the message.

Delivery Information

This section presents information regarding the delivery of the push notification.

Information provided is described as follows:

TitleDescription
ServiceThe service used to send the push notification.
Send AttemptsThe number of attempts to send the push notification.
Start TimeThe time in which the push notification was delivered.
End TimeThe time in which the push notification was received.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard