Known limitations

To send push notifications, Notification Service must be able to send HTTPS requests to cloud endpoints of the according provider.

Similar applies to the client side (Browsers on the client devices), strict firewall or proxy configurations may block the incoming web push notifications. In case of issues, please check the browser vendor documentation about communication requirements.

Please refer to the Push Notification Network Requirements for more information.

Google Chrome requires a TCP connection on port 5228/443 to mtalk.google.com for the Web Push communication. As no standard protocol (i.e. http(s), ssh, sftp, rdp, ftp) is used, some proxy or firewall settings might block the request. In order for the Push Notifications feature to work on Chrome, the respective ports need to be allowed.

Firefox, Safari and Edge are using standard protocols for Web Push.

Once a user has either accepted or declined to receive push notifications, there is no feature provided within Nexeed IAS to change that decision. To retrigger the question on whether to accept or decline push notifications, the user must delete session related browser data. Furthermore, the browser-internal decision must be removed.