-
-
Notifications
You must be signed in to change notification settings - Fork 305
Description
First Check
- This is not a feature request
- I added a very descriptive title to this issue.
- I used the GitHub search to find a similar issue and didn't find it.
- I searched the documentation, with the integrated search.
- I already read the docs and didn't find an answer.
- I can replicate the issue inside the Demo install.
Homebox Version
0.22.3
What is the issue you are experiencing?
When I add OIDC to my homebox instance I am no longer able to log in and the logs produce
ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000064
How can the maintainer reproduce the issue?
I have a working Homebox (docker) instance which I can log into. I also have a working Keycloak instance that I am able to use for other applications.
I add the following configurations
HBOX_OIDC_ENABLED=true
HBOX_OIDC_ISSUER_URL=https://dev.keycloak.home.darkowl.org/realms/master
HBOX_OIDC_CLIENT_ID=home-box
HBOX_OPTIONS_TRUST_PROXY=true
HBOX_OIDC_CLIENT_SECRET=#################
If I am not logged into keycloak it will ask me to log in, then it goes directly back to the login screen. If I try to log in with my username / password It flashes the screen like it is going to log in but takes me directly back to the log in page. Checking the dev console I get 401 errors and in the docker log for the application I see
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000146
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000147
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000148
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000149
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000150
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000151
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000153
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000154
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000152
9:19PM ERR ../go/src/app/internal/web/mid/errors.go:31 > ERROR occurred error="valid authorization token is required" req_id=828f9aaac981/Lx5j16CUdQ-000156
Deployment
Docker (Linux)
Database Type
PostgreSQL
OS Architechture
x86_64 (AMD, Intel)
Deployment Details
As a note, if I take the environment settings out, I no longer see the OIDC login option, but I still can not log in. The only way I have been able to restore functionality is to restore my database from before I enabled OIDC