Configuring a third-party push notification provider on the Avaya Aura Web Gateway

Last Updated : Jun 08, 2026 |

About this task

To use push notifications on third-party iOS applications, you require a third-party push notification provider. An Avaya Breeze Client SDK application developer can implement a third-party push notification provider. Use this procedure to set up or update a third-party push notification provider on the Avaya Aura® Web Gateway.

Before you begin

A third-party Avaya Breeze Client SDK application developer must implement the third-party push notification provider. For more information about push notification provider requirements, see Third-party push notification provider requirements.

Procedure

  1. On the Avaya Aura® Web Gateway administration portal, navigate to Advanced > Push Notification Settings > Provider Settings.
  2. Do one of the following:
    • To add a new provider configuration, click Add.

    • To edit an existing provider, select the required provider from Push Notification Provider and click Edit.

  3. In Enter Company Domain, enter the domain where your Avaya Aura® Web Gateway is deployed.

    For example: mycompany.com

  4. In Push Notification Provider Name, enter a name for the provider.

    For example: MyPushNotificationProvider.

    This name is used in the Avaya Aura® Web Gateway administration portal for display purposes only.

  5. In Push Notification Provider Address, enter the FQDN where your push notification provider is deployed.

    For example: mypushnotifications.mycompany.com

  6. In Push Notification Provider Port, enter the port number for the push notification provider.

    The default port is 443.

  7. Click Generate Key.

    The Avaya Aura® Web Gateway generates a public and private key pair and an identifier. This data is required to authorize Avaya Aura® Web Gateway on the push notification provider. The Avaya Aura® Web Gateway also updates the following values:

    • System Id: A unique identifier for your system.

    • Public Key: A public key.

  8. Click Export.

    Avaya Aura® Web Gateway displays a pop-up window with the authorization data in JSON format.

    The following is an example of the authorization data:

    {
    	"systemId": "9bf8f4ab-99b1-452b-9b7f-e75aacf31d19.mycompany.com",
    	"description": "Avaya Aura Web Gateway Services",
    	"publicKey": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE9rtz4fuYhGm2JlvnI6lZmate8eEX\na4wvmklSdHGYZHos7y8xNBNCEj9wc3klayOKHYIVIeL0ryVFgM16Ud5FDQ==\n-----END PUBLIC KEY-----",
    	"alg": "ES256"
    }
    Important:
    • Do not close the Provider Settings page on the Avaya Aura® Web Gateway administration portal while you are exporting authorization data to your push notification provider.

    • Do not save the data you provided on the Provider Settings page of the Avaya Aura® Web Gateway administration portal until you export authorization data to your push notification portal. Otherwise, the push notification service might not work as expected.

  9. Copy the system ID and public key data and provide it to your push notification provider.
    For example:
    "systemId": "9bf8f4ab-99b1-452b-9b7f-e75aacf31d19.mycompany.com"
    "publicKey": "-----BEGIN PUBLIC KEY-----\nMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAE9rtz4fuYhGm2JlvnI6lZmate8eEX\na4wvmklSdHGYZHos7y8xNBNCEj9wc3klayOKHYIVIeL0ryVFgM16Ud5FDQ==\n-----END PUBLIC KEY-----"
    The steps you must perform to provide authorization data are provider-specific. For more information, contact your third-party push notification provider vendor.
  10. Return to the Provider Settings page on the Avaya Aura® Web Gateway administration portal.
  11. Click Test to verify that your system can connect and authenticate with the push notification provider.
  12. Do one of the following: