Upgraded to 5.17.0, but had to roll back since login broke:
[Wed Feb 25 14:53:44.458545 2026] [wsgi:error] [pid 94060] [remote 129.242.6.226:46890] [Wed Feb 25 14:53:44 2026] [WARNING] [pid=94060 nav.web.auth.middleware] User <username> denied access to /?_=1772027624097 [Wed Feb 25 14:53:44.460908 2026] [wsgi:error] [pid 94060] [remote 129.242.6.226:46890] [Wed Feb 25 14:53:44 2026] [WARNING] [pid=94060 django.request] Unauthorized: /
Neither local users nor ldap-users can log in.
How to debug?
We do not use REMOTE_USER which is mentioned in the release notes.
From webfront/webfront.conf
# Should it be possible to log in with the username set in a request header # (usually REMOTE_USER)? [remote-user] # Whether REMOTE_USER authentication should be enabled enabled = no
--Ingeborg
On Wed 25 Feb 2026 at 15:18, Ingeborg Hellemo via Nav-users nav-users@lister.sikt.no wrote:
Upgraded to 5.17.0, but had to roll back since login broke:
That's interesting. We've deployed NAV 5.17 to more than 45 customers and had no such issues :-/
Neither local users nor ldap-users can log in.
How to debug?
I would first suggest adding `nav.web.auth = DEBUG` to the `[levels]` section of NAV's `logging.conf` configuration file, then restart the web process. Try logging in again and see what gets logged.
-
Ingeborg Hellemo -
Morten Brekkevold