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
I am using Authentik to provide HTTP Basic Auth to Timetagger. I have setup a proxy provider in Authentik which takes the username and password and passes them in X-Authentik-Username and X-Authentik-Password respectively (the default).
Timetagger gives me: unauthorized: The webtoken has expired (after 14 days)
What could be the issue here? Could it be that the error is misleading and actually null is being passed for the username? Authentik and Timetagger are both funning as docker containers on the same host (192.168.0.180) - is that the issue - should I use the docker internal IP address?Could it be that I used to run with fixed users in the docker compose? Am I supposed to generate a token in some way and pass that in?
It is getting through nginx as the reverse proxy which proxy passes to authentik which then forwards to timetagger internally. Authentik is set to pass username and password in the Proxy config in Authentik.
Unhelpfully, there is nothing at all in the docker log for the timetagger container.
Any ideas?
The text was updated successfully, but these errors were encountered:
I am using Authentik to provide HTTP Basic Auth to Timetagger. I have setup a proxy provider in Authentik which takes the username and password and passes them in X-Authentik-Username and X-Authentik-Password respectively (the default).
Timetagger gives me:
unauthorized: The webtoken has expired (after 14 days)
My docker compose has this in it:
What could be the issue here? Could it be that the error is misleading and actually null is being passed for the username? Authentik and Timetagger are both funning as docker containers on the same host (192.168.0.180) - is that the issue - should I use the docker internal IP address?Could it be that I used to run with fixed users in the docker compose? Am I supposed to generate a token in some way and pass that in?
It is getting through nginx as the reverse proxy which proxy passes to authentik which then forwards to timetagger internally. Authentik is set to pass username and password in the Proxy config in Authentik.
Unhelpfully, there is nothing at all in the docker log for the timetagger container.
Any ideas?
The text was updated successfully, but these errors were encountered: