Setting container‘s timezone makes OAuth unusable

[oeiber]

To make it easier analyzing log files, I mounted /etc/timezone to all my containers. But when I do that for my authentic containers this will result OAuth timestamps where delivered to the application with the current time, in my case utc+2, instead of delivering current utc time.

[BobSilent]

I experienced the same issues with oauth and saml.

Simply following the configuration description, which does not tell anything about mounting Timezone or setting an environment, is the success.

I did not experience any disadvantages of not configuring/mounting the timezones.

Authenik does everything right, all is logged in UTC and shown to the user localized.

So either fixing this issue or extending the configuration documentation with a warming would be okay from my perspective.

[BeryJu]

The server assumes that it's local timezone is UTC as configured here https://github.com/goauthentik/authentik/blob/master/authentik/root/settings.py#L321

[septatrix]

It seems like this could easily be supported by using django's utils.timezone.activate?

[pinerolly]

failed to register layer: unlinkat /usr/local/lib/python3.11/site-packages/pkg_resources/_vendor/pyparsing/diagram: invalid argument

can pull the image