What Went Wrong?
I can't login to any of my accounts, I have been using Forward Auth (Remote Auth) all the time.
I discovered the issue before I wanted to upgrade from booklore to grimmory, so both latest versions of booklore and current version of grimmory are affected.
But last time I used the service (maybe december, it was working without issues).
Results into an error
grimmory | 2026-04-05T12:12:51.750+02:00 DEBUG 1 --- [booklore-api] [omcat-handler-1] o.b.controller.AuthenticationController : Remote-Auth: retrieved values from headers: name: null, username: null, email: null, groups: null
grimmory | 2026-04-05T12:12:51.750+02:00 DEBUG 1 --- [booklore-api] [omcat-handler-1] o.b.controller.AuthenticationController : Remote-Auth: remote auth settings: org.booklore.config.AppProperties$RemoteAuth@5bfe0a5a
How Can We Reproduce This?
Enable Forward Auth with following configuration
- REMOTE_AUTH_ENABLED=true
- REMOTE_AUTH_CREATE_NEW_USERS=true
- REMOTE_AUTH_HEADER_USER=Remote-User
- REMOTE_AUTH_HEADER_NAME=Remote-Name
- REMOTE_AUTH_HEADER_EMAIL=Remote-Email
- REMOTE_AUTH_HEADER_GROUPS=Remote-Groups
- REMOTE_AUTH_ADMIN_GROUP=users@example.com
And use a proxy that supplies this headers.
What Should Have Happened?
Auth is skipped, user is authintificated/created following the headrs.
Screenshots or Error Messages (Optional)
No response
Any Ideas on How to Fix This? (Optional)
I have found this PR https://github.com/grimmory-tools/grimmory/pull/128/changes, which might be solving it.
Unfortunatelly, my proxy middleware always enforces capitalized headers even if I set them to all lovercase. So I can't test if this is a case.
Your Setup
Grimmory: latest docker image (2.3.1 as a moment of writing)
Before Submitting
What Went Wrong?
I can't login to any of my accounts, I have been using Forward Auth (Remote Auth) all the time.
I discovered the issue before I wanted to upgrade from booklore to grimmory, so both latest versions of booklore and current version of grimmory are affected.
But last time I used the service (maybe december, it was working without issues).
Results into an error
How Can We Reproduce This?
Enable Forward Auth with following configuration
And use a proxy that supplies this headers.
What Should Have Happened?
Auth is skipped, user is authintificated/created following the headrs.
Screenshots or Error Messages (Optional)
No response
Any Ideas on How to Fix This? (Optional)
I have found this PR https://github.com/grimmory-tools/grimmory/pull/128/changes, which might be solving it.
Unfortunatelly, my proxy middleware always enforces capitalized headers even if I set them to all lovercase. So I can't test if this is a case.
Your Setup
Grimmory: latest docker image (2.3.1 as a moment of writing)
Before Submitting