Reconfiguring the Avaya Push Notification provider after upgrade or migration

Last Updated : Jun 10, 2026 |

About this task

After you upgrade or migrate to Release 3.8, Avaya Aura® Web Gateway continues to use apnp.avaya.com as the default provider address for the Avaya Push Notification provider. Avaya recommends that you use the pnp.avaya.com domain instead. Since you cannot update or delete the default Avaya Push Notification provider, you can configure a new provider with the pnp.avaya.com provider address.

This procedure only applies if you are upgrading or migrating to Release 3.8. If you are performing a fresh installation, Avaya Aura® Web Gateway will use pnp.avaya.com as the default provider address for the Avaya Push Notification provider.

Procedure

  1. On the Avaya Aura® Web Gateway administration portal, navigate to Advanced > Push Notification Settings > Provider Settings.
  2. Click Add to add a new provider configuration.
  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: AvayaProviderUpdated.

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

  5. In Push Notification Provider Address, enter pnp.avaya.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 information in JSON format. You must provide this data to your Avaya Cloud account.

    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 until you finish exporting authorization data to your Avaya Spaces account.

    • 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 Avaya Cloud account. Otherwise, the push notification service might not work as expected.

  9. Copy the authorization data, including the surrounding curly brackets, and save it in a file on your computer.
  10. In a new browser tab, log in to your Avaya Cloud account and navigate to Manage Companies.
  11. Select the required company and navigate to the Apps tab.
  12. From App, select Avaya Mobile Push Notification Service.
  13. In Data Configuration, select the JSON check box.
  14. Replace the content in Public Settings with the content of the file that you created and then save your changes.

    You must ensure that the authorization data you enter in Public Settings is a valid JSON string. If the data uses an invalid format, the Avaya Spaces account displays a warning message, but still allows you to save changes.

    The Avaya Spaces account stores authorization data internally. Public Settings only displays the authorization data that you entered last. You will not lose any previously entered authorization data if you overwrite existing content with the new authorization data.

  15. Return to the Provider Settings page on the Avaya Aura® Web Gateway administration portal.
  16. Click Test to verify that your system can connect and authenticate with the push notification provider.
  17. Do one of the following:

Next Steps

  • Update the firewall rules for the pnp.avaya.com domain.

  • Update push notification configurations for mobile applications.

Related information
Firewall configuration
Updating mobile application settings