Notification Registration

To be able to use push notification messages for remote authentication and remote transactions, the Customer Mobile Application must complete a notification registration process.

Notification registration consists in obtaining a notification identifier from the Push Notification Service, and in transmitting it to the OneSpan Trusted Identity platform via a dedicated orchestration command. The notification identifier is unique per device and per app.

For more information, refer to the Notification SDK Integration Guide at Mobile Security Suite Integration Guides.

The notification registration process can only be completed if the Customer Mobile Application has been activated (see Activation); this process must take place after a successful activation (mandatory for finalizing the activation flow on the server-side) and at application startup (only if the notification identifier has changed).

Notification registration is mandatory for finalizing the activation process on the server-side.

Notification registration workflow illustrates the notification registration workflow.

1. The Customer Mobile Application calls the registerNotificationService method of the Notification SDK to obtain a notification identifier.

2. The Notification SDK contacts the Push Notification Service to obtain a notification identifier.

3. The Notification SDK returns to the Customer Mobile Application a OneSpan Notification Identifier, which is an abstraction of the previously retrieved notification identifier.

4. The Customer Mobile Application calls the startNotificationRegistration method of the Orchestration SDK to start the notification registration process.

5. The Orchestration SDK builds an orchestration command which includes the OneSpan Notification Identifier and transmits it to the Mobile Application Server using the onNotificationRegistrationComplete method.

6. The Customer Mobile Application transmits the orchestration command to the Customer Application Server.

7. The Customer Application Server calls the orchestration-commands Web service of the OneSpan Trusted Identity platform by providing the orchestration command. A new orchestration command is returned as a result.

8. The Customer Application Server transmits the orchestration command to the Customer Mobile Application as a response to the previous request.

9. The Customer Mobile Application calls the execute method of the Orchestration SDK to finalize the notification registration process.

10. The Orchestration SDK calls the onNotificationRegistrationSuccess method to notify the Customer Mobile Application.

After a successful notification registration process, the OneSpan Trusted Identity platform is able to send push notification messages to the Customer Mobile Application.

The Customer Mobile Application must integrate the other methods of the Notification SDK to properly receive and process the push notification messages sent by the OneSpan Trusted Identity platform.

For more information about integrating this feature, see Notification registration.