Skip to main content
Question

Enabling Push Notifications results in bad request error

  • November 6, 2025
  • 3 replies
  • 75 views
Stijn Schuurman
Vanguard
Forum|alt.badge.img+1

When following the guide for enabling push notifications for the platform 2025.3 update.

I encounter the following problem:

Summary
URL: https://_____.nl/indicium/web-push/public-key
Status: 400 (Bad Request)

The guide registered under the platform upgrade 2025 3 is what I have followed.

https://docs.thinkwisesoftware.com/blog/2025_3

For good measure, the .pem file with the public keys has been created on the IIS webserver.

It seems that Universal GUI is not reaching out to Indicium in the proper way. Henceforth, the bad request error (400).

It is not stated in the documentation, where such an error could be coming from.

3 replies

D
Moderator
Forum|alt.badge.img+3

Did you configure the e-mail address for push messages in the global settings in IAM?

This is mandatory, so vendors like Microsoft, Google & Mozilla can contact you in case of abuse with the push notifications on their platforms.

Regards,

Dick van den Brink

Stijn Schuurman
Vanguard
Forum|alt.badge.img+1

​@Dick van den Brink 

Absolutely!  The steps in the guide have been followed. Including setting the e-mail address.

 

Nick Janssen
Hero
Forum|alt.badge.img+5

Hi Stijn,

Apologies for the late reply.

Are you still experiencing the issue? If so, could you register a ticket in TCP?

From there, we will investigate the issue in more detail.
 

Could you also include a .HAR file as an attachment in which the failing request is done to Indicium?
You can download a .HAR file in your browser’s dev tools > Network tab > Download HAR file

Best regards,
Nick Janssen

Terms & ConditionsCookie settingsAccessibility statement