LDAP - time zones selection not applied

[keguira]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

Version

10.0.5

Bug description

After activating the time zone in database all of the application take it into account (users, general configuration, etc) except of the LDAP configuration.

In the following elements, the selector still indicates GMT offsets in place of timezone selection :

• Setup > Authentication > Setup
• Setup > Authentication > LDAP directories > "an element" > Advanced information

For information : I also raised a ticket on documentation to further the impacts of these configurations and how they interact with everything else as time handling can be hard to understand.

Relevant log output

No response

Page URL

No response

Steps To reproduce

1. create a new instance of GLPI
2. Activate timezones like asked in documentation
3. Create a new LDAP configuration

Your GLPI setup information

No response

Anything else?

I use a single instance of GLPI with multiple LDAP directories located around the world. Users have their own timezone, Active directories servers have their own time zone (north america, north africa, multiple countries in europe).

[cedric-anne]

As far as I see, these offsets are used to recompute the modifytimestamp field to a GMT date that is then stored in the date_sync field of the user, in order to be compared, on next synchronization, with the modifytimestamp recomputed the same way, to determine whether the user has been updated.

When timezones are enabled in GLPI, timestamps are converted from current user timezone to GMT when inserted in DB, so date_sync field value is should be converted to a timestamp in current user timezone instead of GMT. I do not know if it is more than a display bug here. A test should probably be added in our test suite to verify that all works as expected.