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
Hello. I'm using version 0.42.0 behind reverse proxy with oidc and site prefix.
The oidc part works (using keycloak) but oidc_protected_paths and oidc_public_paths do not use site_prefix! I have to provide absolute paths.
Is it on purpose?
By the way it is an awesome tool :-)
Ideally the user would specify oidc_protected_paths and oidc_public_paths without the site prefix in the configuration, and we would still protect the path with the prefix.
changed the title [-]Hello. I'm using version 0.42.0 behind reverse proxy with oidc and site prefix.[/-][+]oidc_protected_paths and site prefix[/+]on Jan 27, 2026
If that helps add these lines in src/webserver/oidc.rs near line 103
Sorry not tested it and best bet using AI.
Must add tests for edge case (ie when unset or empty, do not add site_prefix)
Activity
[-]Hello. I'm using version 0.42.0 behind reverse proxy with oidc and site prefix.[/-][+]oidc_protected_paths and site prefix[/+]billy34 commentedon Jan 27, 2026
If that helps add these lines in
src/webserver/oidc.rsnear line 103Sorry not tested it and best bet using AI.
Must add tests for edge case (ie when unset or empty, do not add site_prefix)
lovasoa commentedon Jan 27, 2026
@billy34 can you open a pull request ? I'll comment there directly !