Push Notification

View this page for | |

Your mobile app can optionally receive information for validation requests (authentication, transactions, etc.) via Microsoft WNS Microsoft Windows Push Notification Services push notifications.

Set Up Push Notifications

To configure push notifications for your app, you need to:

• Give your app the correct capabilities/privileges - go to Windows Push Notification Services (WNS) Overview

• Obtain credentials using your developer account in order to configure the HID authentication platform so it can send push notifications to your app - go to How to authenticate with the Windows Push Notification Service (WNS)

• Configure an Out-Of-Band Delivery Gateway in the HID authentication platform. For example:

  • Create a Notification hub in Microsoft Azure with your own account.
  • Configure an Out-Of-Band Delivery Gateway with an Azure WNS Push Delivery adapter in:
    • ActivID AS
    • ActivID Appliance
    • HID Authentication Service (API integration)

To enable push notifications for your app, you need to request the user permission for your app.

Push Notification Messages

Android, iOS and Windows push notification systems manipulate JSON messages. These messages can have proprietary members, configured in the HID authentication platform (in the OOB Delivery Gateway) and parsed by the mobile application.

Provisioning Notification Example

The prov value is a JSON object. The application retrieves it, serializes it, and passes it to the SDK (ContainerInitialization.activationCode).

Sample Provisioning Notification

{
    ... (members expected by the operating system) ...
    
			"prov": 
{...}
}

Transaction Signing Notification Example

The tds value is the Transaction identifier to be passed to the Device.retrieveTransaction method.

Sample Transaction Signing Notification

{            
    ... (members expected by the operating system) ...
    
	"tds": "<transaction id>"> 
}