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 can recreate the issue with all plugins disabled
Describe the issue
Hi,
Client's timezone in the browsers is not auto detected (and the fallback to the server timezone occurs) in case oauth2 authorization is configured with the setting oauth_login_redirect set to true.
The reason is probably due to the fact that currently the auto detection of the timezone occurs in the login form:
The problem leads to the incorrect and unexpected message(s) time display for the most users (who have the timezone set to Auto, which is the default).
As OIDC authorization becomes more common, I would say this is an issue worth looking into.
My current workaround is to set the server's php variable date.timezone explicitly to the value that matches the timezone of the most users. OIDC use case likely means it is deployed for organizations with a substantial user base, so this issue may have a significant impact on such deployments.
Prerequisites
Describe the issue
Hi,
Client's timezone in the browsers is not auto detected (and the fallback to the server timezone occurs) in case oauth2 authorization is configured with the setting oauth_login_redirect set to true.
The reason is probably due to the fact that currently the auto detection of the timezone occurs in the login form:
roundcubemail/program/js/app.js
Line 668 in 6e216b5
In case of oauth authorization set and with the oauth auto redirection configured the login form is bypassed.
What browser(s) are you seeing the problem on?
Chrome, Edge, Firefox, Safari
What version of PHP are you using?
v8.3
What version of Roundcube are you using?
v1.6.9
JavaScript errors
No response
PHP errors
No response
The text was updated successfully, but these errors were encountered: