Closed litbea closed 6 months ago
I don't understand this issue or maybe it's a misunderstanding of what is defined, where and "what for" (and maybe a label thing)
The timezone (or offset by default) defined in Setup > General > Default values
corresponds to the time zone applied by default for all users unless you ovewrite it at user-level.
This configuration handles the timezone function (Europe/Lisbon for example).
In authentication
, the offset (and not timezone compliant) corresponds to an offset applied in the use case of ldap sync . It's the time_offset
value stored in glpi_config
table and it seems to be a legacy thing. This is not used anywhere else.
There is no place in GLPI where you declare your server-side configurated timezones / offsets (OS, mysql/mariadb and php levels) as they can use a specific value or the OS one.
As for version 10.x and 11.x, all points in time (datetime) are still stored as TIMESTAMP
(so relative to UTC with a range from 1970
to 2038
).
I'm sorry, but there is no "server timezone" in my Setup > General > Default Values panel. I'm currently using version 10.0.14. That may explain my confusion, I now understand the auth offset is a different parameter.
The problem is myself and my misspell : it's not a server timezone, just a display "timezone" in personnalisation. This is the one i'm talking about in the first paragraph. Corrected.
Those are indeed two distinct settings. The one in auth file is specific to authentication and is present in very old GLPI versions.
Code of Conduct
Is there an existing issue for this?
Version
10.0.14
Bug description
GLPI server time zone should be located in Setup > General, instead of /front/auth.settings.php in my opinion.
Relevant log output
No response
Page URL
/front/auth.settings.php
Steps To reproduce
No response
Your GLPI setup information
Information about system installation and configuration
Server
GLPI constants
Libraries
LDAP directories
SQL replicas
Notifications
Plugins list
Anything else?
No response