You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Broader than that, just like Open Zaak we need to support Open Notificaties behind API gateways. This means exposing the API via a gateway-domain with a path prefix and having the admin of Open Notificaties remain available via a separate domain name.
This is done in Open Zaak with the OPENZAAK_DOMAIN and OPENZAAK_REWRITE_HOST options. Similar envvars will be necessary to ensure the proper URLs are used when Open Notificaties is behind an API gateway
Similar to Open Zaak, the CSRF_TRUSTED_ORIGINS setting is also one that would be necessary for Open Notificaties
open-zaak/open-zaak#1566
Broader than that, just like Open Zaak we need to support Open Notificaties behind API gateways. This means exposing the API via a gateway-domain with a path prefix and having the admin of Open Notificaties remain available via a separate domain name.
This is done in Open Zaak with the OPENZAAK_DOMAIN and OPENZAAK_REWRITE_HOST options. Similar envvars will be necessary to ensure the proper URLs are used when Open Notificaties is behind an API gateway
https://open-zaak.readthedocs.io/en/stable/installation/reference/fq-urls.html?highlight=OPENZAAK_DOMAIN
Needed/Expected for Amsterdam (APIM) and Rotterdam (HIP)
Related issue for the Objects API: maykinmedia/objects-api#388
The text was updated successfully, but these errors were encountered: