Hanne Moa

Missing: configuring this via NAV's own config files.

Django 4.2 and later fails on the integration tests and functional tests because form-rendering is changed and the foundation 5 theme we use for django-crispy-forms do not support the new...

In github actions, some functional tests fail. - FAILED tests/functional/geomap_test.py::test_geomap_loaded - AssertionError: ... - FAILED tests/functional/navbar_test.py::test_simple_ip_search_should_return_result - FAILED tests/functional/status_test.py::test_panel_should_toggle_when_clicked - FAILED tests/functional/status_test.py::test_remember_last_panel_state - sele...

I'm starting to wonder if all of this is better to do in the external webserver, since we need it both for NAV and for the non-NAV code.

> ```shell > docker volume rm nav_nav_cache > ``` Sounds like a good candidate for a "make nuke"-rule.

My `make nuke` involves `docker system prune` =) Nuke it from orbit, it's the only way to be sure!

> Bug in Netmap. When I go to Netmap tool on web, an alert pops up. There is a `500 Internal Server Error` on `GET .../netmap/grapgh/layer2/...`. Fresh install of NAV,...

This is a continuation of #2859? I'd rather not review this one until that one is merged and this one updated accordingly.

Django already supports this, it is only a matter of using the existing functionality and wrapping it in our own config-system. https://docs.djangoproject.com/en/3.2/topics/auth/passwords/#module-django.contrib.auth.password_validation

Example policy we need to easily support: * A minimum of any N characters, N configurable * A minimum of M (less than N) characters, M configurable, plus: 1. A...