Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

As a devops/architect I want to expose Open Notifications on a different domain for the API than for the admin #126

Open
alextreme opened this issue Feb 5, 2024 · 0 comments
Labels

Comments

@alextreme
Copy link
Contributor

alextreme commented Feb 5, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant