This documentation provides details about push notifications payloads that may be useful to integrate the inWebo mAccess authentication feature into an iOS and Android mobile application. It is intended for developers.

In an application that integrates mAccess, the push notifications sent are from the "Message" class of Firebase. They contain payload data. Here are the push notifications payload details:

{
"CollapseKey":"",

"Data":{
    "serviceName":"",
    "deviceAlias":"",
    "action": "",
    "serviceid":"",
    "alias":""
},
"content_available": true

"From":"",
"MessageId":"",
"SenderId":"",
"SentTime":""
}
CODE

  • The CollapseKey is set in the inWebo administration console, in the service configuration.

  • The information sent by inWebo is in the "Data" object.

  • content_available is a boolean. When set to true, an inactive client app is awoken, and the data is sent through APNs as a silent notification and not through Firebase Cloud Messaging.

  • Firebase manages the following data: "From", "MessageId", "SenderId", "SentTime"

Find more information in the Firebase Reference documentation: https://firebase.google.com/docs/cloud-messaging/http-server-ref