Configuring 'notificatiecomponentconfiguratie' in Open Notificaties leads to a HTTP 500 error when viewing the configuration

[alextreme]

Taiga Utrecht 322

Configuring 'notificatiecomponentconfiguratie' in Open Notificaties leads to a HTTP 500 error when viewing the configuration. This after upgrading from Open Notificaties 1.6.0 to 1.7.1

Service 'https://domainname/api/v1/' is not known in the client registry. Did you load the config first through Client.load_config(path, **manual)?

Removing the 'notificatiecomponentconfiguratie' ensures the configuration is accessible again, however according to the Open Zaak documentation the 'notificatiecomponentconfiguratie' should be configured in order to keep the authorizations in-sync:

https://open-zaak.readthedocs.io/en/latest/installation/config/openzaak_config.html#id3

[Coperh]

Seems to be fixed with the new version of notifications API common

[alextreme]

Good to know, @danielmursa-dev please double-check this in preparation of the new release for Open Notificaties after that this issue can be closed

[danielmursa-dev]

Checked, also for me is configured!